Repository navigation
Feature-Request: Linking "Objects" together #7435
Description
Activity
cc @karlitschek
I agree that this would be a great feature. Especially for collaboration. The challenge is probably the right user interface for this
the proposal of @frogueat would allow an extension of the contacts popover concept....
if I have "@Calendar:20171209/mytitle" in a comment, show a popover with some info on the calendar item; then, if I click on the popover, show me the calendar item. The same is true for "@file:xxx" or "@task:xxx" or ...
It could be elegant from an user interface point of view, even if not technically easy to realizeI am happy to see, this idea finds some interest! To push it further i'd like to make you familiar with the concept of backlinks (I know this from a different dms/ecms/wf/cloud-product). Logically this is simple: linking an object implicates that the linked object (the target) sees the object fomulating the link (the source). This helps users much in exploring the "network" and generates very useful information.
Example: 2 Calendar items (item1, item2) links a file. At the file in the backlinks you see 2 links: one to item1, one to item2.
The challenge here is the removing the backlinks too, if the link is removed.
Example: The above calendar item1 removes the link to the file. At the file in the backlinks you see only the link of calendar item2.
As I wrote in #11015 (maybe it fits better in here): I think the key challenge - beside the UI - is to have an extensible concept so that other apps could add their own "things" the users can reference from other apps. E.g. if I would write a recipes app I would "instantly" be able to reference a recipe in a calendar appointment and vice versa (e.g.
@recipe:steak-with-fries). Maybe something like a publish/subscribe service for object referencing:- The app
Asubscribes to the "linking service" (let's call itLinker), telling the service- a unique keyword,
- the URL to resolve a "linked object" and
- an API endpoint for loading autocompletion entries.
- The user types
@<keyword>:in appB. This triggers an API call toLinker's auto completion endpoint (as soon as the user types the first character after:). That endpoint would then call the corresponding endpoint registered by appAto load the autocompletion entries and to return them to appB. - And finally, app
B's UI could trigger API calls toLinker's endpoint for adding hyperlinks to referenced objects.
That would be the general flow for a basic version. I could think of some more neat features - like registering templates for popovers or adding additional columns for the autocomplete / search function (e.g., when you want to reference the recipe "Steak with Fries" but you type something that is only mentioned in an additional description field).
Opinions? Suggestions?
- The app
Linking Documents / Related documents is a powerful form of NLP document management. This is one of the fastest growing fields and NextCloud's competitor's all support it right now. SpringCM is probably the furthest along.
The ideal thing is while "tags" are great. But, tags aren't easily accessible. You can't see them in the sidebar. To link objects together, tags are a great direction. But, part of it is similar to how SpringCM does it via Additional Fields/Attributes.
These Attributes let me link a Sub-Contract to a Contract. So in the sidebar I can click on the "parent contract" or see other sections.
@jancborchardt it is interesting.
We did not really took a stance on this, any thoughts?Reacted by Spartachetto
Steps to reproduce
Expected behaviour
It would be great to have the posibility to link Objects together. E.g. to reference in a calendar-item a file, a user, a note, a task or something else. Therefor a notation would be necessary - like in confluence or here on github ... Something like @[instanceuri->]class:name. E.g. referencing a file in a calendar-item would be @file:/documents/mydocs/myfile.txt. In an md-File referencing a calendar item cold be @Calendar:20171209/mytitle and so on ...
It could be than a clickable link on the link and pretty embedding (thinking on youtube-links in fac_bo_k) of the object would be possible ...
Sure, that's not simpel - but wouldn't it be great ;-)