Reverse tree relationship #33
Labels
No labels
area/api
area/content_model
area/framework
area/infrastructure
area/io
area/presentation
area/preservation
area/rdf
area/security
area/submission
area/ui
p
critical
p
high
p
low
p
medium
s
blocked
s
done
s
progress
s
testing
s
wontfix
t
bug
t
documentation
t
enhancement
t
feature
t
test
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
scossu/pocket_archive#33
Loading…
Add table
Add a link
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?
In order to have a complete independence of curatorial resources from trees, the
has_treeproperty should be reversed and a RDF relationship should be instead established from the tree to the resource. This triple should be kept in the tree graph for easier cleanup.has_treecan still be used in a submission as it is now, as a boolean value to indicate that a tree should be generated for a resource. When re-generating the LL, this field can be set totrueif a tree is found, orfalseotherwise.