#Manually Managable Node References

9 messages · Page 1 of 1 (latest)

untold elk
#

The goal is to allow the user to manage the node reference in a manner more like the current version. i.e. being able to copy and paste a block reference.

This is very useful for me in the current version.

Some example use cases

  1. A 'waiting' or 'pending' property to connect dependent tasks
  2. Putting a given task in an agenda for a meeting that your manually compiling.

With the new DB version we can use the 'node reference' command however we can't simply copy and paste a block reference and have it resolved. It seems the node reference isn't human editable in any way so you have to search for the block and while 'page nodes' can be namespaced for easier location and typically have more unique title-like names blocks may be anything. Blocks often have the same text and only their context differentiaties them. e.g. 'Prepare Paperwork' task for an overall 'prepare audit' task.

Using the above examples

  1. You might need to request paper work for an upcoming audit from someone but you're only missing the paperwork from one particular month. Currently I would simply copy the block reference and paste that into the 'pending' property of the 'Prepare Audit' task and then I could easily see what I'm missing to finish preparing the audit. With the DB version as it is I'd have to search and scroll through a lot (I do a lot of audits) to find the right one.

I think being able to simply copy and paste a reference and have it resolved into a node reference would be a great improvement.

The reason the search feature on the nodes isn't sufficient is that while you can see the context of each node when searching for a node there's no way to filter other than the text in the node which for some tasks might be similar or identical.

How it would work:

My suggestion is to simply have a uuid as with the current 'block reference' and when searching for a node the search box looks for uuid and text in the block. Hence pasting in the UUID will autmatically find the block.

upbeat pond
#

Hi, Im not sure if this is what you are looking for but you can copy the reference to a block by right clicking on its bullet point and selecting "Copy block reference"

untold elk
#

@upbeat pond Yes I did notice that but when I paste that somewhere it doesn't resolve into the block in the new version the way it currently does.

Also if you have a property which takes only a node as a reference guy can't then paste in that copied references like you can currently.

Is that what you find out does it work differently for you?

upbeat pond
upbeat pond
untold elk
# upbeat pond What do you mean by "it doesnt resolve into the block"? If I copy and paste a bl...

Thanks for mentioning this.

Well when I've tested on test.logseq.com I can right click a block and click 'Copy Block Reference'. But if I paste that somewhere it's just blank. Is that just me?

I said 'resolve' just because it seemed to convert it into a different format so that when you click it you're editing the original target than editing a block with a reference (i.e. how it currently works)

*Actually when it doesn't even put it into my paste bin on when I click 'Copy Block Reference' anymore.

#

Update: Something appears to have changed recently 🤔.

Now when I use the 'node Reference' command it gives me [[]] with the uuid of the block in trying to reference inside 🤔. Which you can then paste anywhere like your can a block reference in the current Non-DB version.

I'm sure it didn't do that last time I tried.
Actually it seems to be working the old way on Android and a different way on my computer 🤔.

Maybe I might have to wait till they've finished if there in the middle of something 😬.

upbeat pond
untold elk