ktx/pocket_archive
1
0
Fork 0
Code Issues 28 Pull requests Releases 1 Packages Wiki Activity Actions

Reverse tree relationship #33

New issue
Open
opened 2026-01-30 23:14:22 +00:00 by scossu · 1 comment
scossu commented 2026-01-30 23:14:22 +00:00
Owner
Copy link

In order to have a complete independence of curatorial resources from trees, the has_tree property 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_tree can 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 to true if a tree is found, or false otherwise.

In order to have a complete independence of curatorial resources from trees, the `has_tree` property 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_tree` can 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 to `true` if a tree is found, or `false` otherwise.
scossu added this to the v1.0.0 RC milestone 2026-01-30 23:14:22 +00:00
scossu commented 2026-03-25 02:27:11 +00:00
Author
Owner
Copy link

Not critical for release. Deferring to 1.0.0 for now.

This is still desirable, and if production systems start adopting the current trees, a migration tool would be necessary, so it's best to resolve it sooner than later.

Not critical for release. Deferring to 1.0.0 for now. This is still desirable, and if production systems start adopting the current trees, a migration tool would be necessary, so it's best to resolve it sooner than later.
scossu modified the milestone from v1.0.0 RC to v1.0.0 2026-03-25 02:27:19 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
test
v1.0rc1
v1.0b13
v1.0b12
v1.0b11
v1.0b10
v1.0b9
v1.0b8
v1.0b7
v1.0b6
v1.0b5
v1.0b4
v1.0b3
v1.0b2
v1.0b1
v1.0a9
v1.0a8
v1.0a7
v1.0a6
v1.0a5
v1.0a4
v1.0a3
v1.0a2
v1.0a1
v1.0a0
Labels
Clear 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
The issue is blocking major development tasks, is causing significant issues, or is a security/data integrity threat. It must be resolved before all other issues and must be in the current milestone.

  
p
high
The issue is causing notable problems. It must be in a milestone. It must be resolved in order for the milestone to be completed.

  
p
low
The issue may be in a milestone. It may be moved to another milestone or unassigned one, if necessary.

  
p
medium
The issue may be in a milestone. It should be completed in order to close the milestone.

  
s
blocked

  
s
done

  
s
progress

  
s
testing

  
s
wontfix

  
t
bug

  
t
documentation

  
t
enhancement

  
t
feature

  
t
test

  
p
critical
A major malfunction, data corruption, or missing critical feature. Should be resolved ASAP and a new release cut immediately after fixing.

  
p
high
A bug that causes significant disruption or missing or incomplete feature that impairs basic workflows. It must be resolved within the current milestone.

  
p
low
A bugfix or enhamcement request that does not affect normal usage significantly. It MAY be in a milestone.

  
p
normal
A bug or missing feature that causes some disruption or forces annoying workarounds. It SHOULD be in a milestone.

  
t
bug

  
t
documentation

  
t
enhancement

  
t
feature

  
t
test

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
p
critical
p
high
p
low
p
normal
t
bug
t
documentation
t
enhancement
t
feature
t
test
Milestone
Clear milestone
No items
No milestone
v1.0.0
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
ktx/pocket_archive#33
No description provided.