Support inverse relationships #82
Labels
No labels
area/api_cli
area/apps
area/content_model
area/framework
area/infrastructure
area/integrity
area/io
area/presentation
area/preservation
area/rdf
area/security
area/submission
area/ui
s
blocked
s
done
s
progress
s
testing
s
wontfix
p
critical
p
high
p
low
p
normal
t
bug
t
documentation
t
enhancement
t
feature
t
test
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
ktx/pocket_archive#82
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Add a schema configuration option that allows the definition of an inverse relationship for resource-based properties.
E.g., if a
contributorproperty is defined and has aresourceas target, the resources pointed to by this property should display a virtual property (i.e., in presentation only)contributed_tothat points back to the previous resource.This would allow to display bidirectional links in the presentation. It has no semantic value, and it shall not infer the reverse relationship in the database.
A few metadata points are required to display the relationship properly. E.g. for
contributor.Optionally, as part of this ticket, a
PROP_REFLECTflag, mutually exclusive with theinversedefinition, can be defined. This would define a reflexive property, i.e. a property with an inverse that is exactly the same property (e.g.,sibling).