The active wiki for the Samvera Community can be found here: https://samvera.atlassian.net/
This wiki space is archived. The active wiki for the Samvera Community can be found here: https://samvera.atlassian.net/
Time: 9:00am PDT / Noon EDT
Call-In Info: 1-641-715-3660, access code 651025
Moderator: steve van tuyl
Notetaker: Carolyn Cole
Roll call by timezone per following order - ensure notetaker is present (moderator)
folks outside North and South America
folks who were missed or who dialed in during roll call
git tag -d TagName && git push origin :refs/tags/TagName
There appears to be a logical disconnect between the PCDM implementation of Collections and the validation of nesting collections:
For PCDM the "parent has_member child" relationship is defined, and managed on the parent.
For the Nesting collections, we require that:
* The child is EDIT-able by the user
* The parent is READ-able by the user
The Nesting collections requirement implies that the PCDM relationship is pointing in the wrong direction. And Jeremy may have misread the spec, but is still concerned about the direction of the relationship.
Collection or a Collectible A collection hasMember Collectible only for collections. For works the membership was reversed for performance reasons.
Currently to add something to a collection I must have edit permissions on both the collection and the work
Is it ok to collect something that I do not have edit rights for it?
User collection of things I can see (view access) to track things I like
I am a staff member who can create collections, but I do not have edit permissions to the collection
Currently the UI does not allow users with view access to add items to a collection.
Ordering would be the only technical reason to not change the reverse, but it would be really weird to have ordered collections with unordered works
Create a collection membership entity that would handle the order conceptually
would allow you not to have edit access in the work you are collecting
would need to be in fedora
could persist the ids only but that has linked data implications
Flip the relation to get the performance and add an order table in the database
Edit permission to the predicate, but not permissions to the entire work.
Thinking about property permissions
If I can collection something I can change that one and only property
Put up a PR with the rationale and let the community review the PR for this