Okay, thanks for the heads-up @brsma , I will read up on aliases!
Is it entirely possible, also, that my “problem” could be resolved from learning more about the query structure/syntax?
For example, rather than pulling up “all” of, say, page “Section 1.2” (which has since been tied to numerous documents), would a custom query allow me to pull up ONLY those parts of “Section 1.2” that are tied to, say, “Client ABC”? Perhaps if I structure the page’s content differently? (Right now it’s just a parent level block)
Because the situation I’m running into with relying on namespaces is
- they become long
- Client ABC/Agreement X/dtd YYYYMMDD/Section 3.4
- Client DEF/Agreement Y/dtd YYYYMMDD/Section 3.4
- are fairly rigid and hard to edit later down the line if needed
If I’m reading you correctly, an alias could be used to identify THIS portion of the “master” page “Section 3.4” applies to THIS agreement, THAT portion of page “Section 3.4” applies to THAT agreement. And with that, kind of back away from overly granular namespaces. (Am I understanding that incorrectly?)
Or perhaps I could use tags throughout different blocks as a means of identifying and pulling out relevant portions?
Because “locking” things into strict namespaces feel wrong… Like it’s going against the fluidity and ease that a tool like Logseq seeks to provide.
I still have a lot to learn about Logseq, reading through threads like this one, which I can see also mentions the use of aliases: