...
Roll call by timezone per following order - ensure notetaker is present (moderator)
folks outside North and South America
Eastern timezone
Central timezone
Mountain timezone
Pacific timezone
folks who were missed or who dialed in during roll call
- Remind everyone to sign in on agenda.
- Welcome all newcomers!
- Agenda (moderator)
- hydra-pcdm Ancestor Validation for Collection/Sub-Collection Nesting (James Griffin)
- https://github.com/samvera/hydra-pcdm/issues/245
- Note: I've spoken to Lynette earlier today, and given that she is unavailable for the call this week, this issue will be added to the agenda for next week
- Developer's congress communication: making an announcement (Anna Headley)
- Samvera Docs WG rejuvenation (Andrew Myers)
- Add agenda items here
- hydra-pcdm Ancestor Validation for Collection/Sub-Collection Nesting (James Griffin)
- Moderator & notetaker for next time
- Moderator:
- Notetaker:
- After call, this week's notetaker should create the agenda for the next call:
Open template agenda titled "Samvera Tech Call 2019-xx-xx"
- Click on ... in the top right corner, and select copy.
- Popup will open for location. It should contain:
- Space: Samvera
- Parent page: 2019
- Select copy. New page should be created.
- Modify the title to remove "copy of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish.
- PR Review
- Review issues:
- PR review coordinator for next time:
Notes
hydra-pcdmDon't
- https://github.com/samvera/hydra-pcdm/issues/245
- This issue addresses cases where adopters of hydra-pcdm are able to create two Collections, and permit each to be a member of the other (Collection A is a member of Collection B and Collection B is a member of Collection A)
- There was originally a test for this which verified that this type of recursive membership could not be assigned
- LaRita:
- Confirmed, does not remember if it was a direct
...
- ancestor or an ancestor higher within the tree, but one could add a Collection both as an ancestor and as a descendent of another Collection
- This
...
- did bypass validation functionality
- This might have been introduced with the inversion of certain predicates for membership with https://github.com/duraspace/pcdm/pull/31 and https://github.com/samvera/hydra-pcdm/pull/227
- Anna:
- Is this a Hydra PCDM implementation question?
- Hydra PCDM did block this from happening, so this decision was made
- Trey:
- It's not a directed graph in PCDM, so you can have circular relationships
- This was prevented in order to avoid infinite recursion within caching mechanisms for active_fedora
- If this were resolved in hydra-pcdm, would this simplify the nesting indexer in Hyrax?
- LaRita:
- Uncertain, there is a lot of querying happening to avoid nesting loops
- If we could catch an error which is raised, that might be more efficient...
- But the queries are still going to be used to recommend nestable collections
- If we implement this, it might make it harder to Hyrax
- LaRita is hesitant to remove the Hyrax queries
- It would still provide an extra safeguard even if it were supported in hydra-pcdm
- Trey:
- Inclined to recommend that we close the ticket
- Hyrax has solved the problem, and the PCDM specification itself says that it is valid
- LaRita:
- Has no strong feelings
...
- Is fine with closing it
...
- Will proceed by tagging Lynette on the issue
...
- , and then move to close the issue
Samvera Connect 2019 and the Developer Congress
...