Page Comparison

...

1. Roll call by timezone per following order - ensure notetaker is present (moderator)

   1. folks outside North and South America

   2. Eastern timezone

   3. Central timezone

   4. Mountain timezone

   5. Pacific timezone

   6. folks who were missed or who dialed in during roll call

   7. Remind everyone to sign in on agenda.
   8. Welcome all newcomers!
2. Agenda (moderator)
   
   1. hydra-pcdm Ancestor Validation for Collection/Sub-Collection Nesting (James Griffin)
      1. https://github.com/samvera/hydra-pcdm/issues/245
      2. 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
   2. Developer's congress communication: making an announcement (Anna Headley)
      1. Developer Congress - Monday 21st October 2019
   3. Samvera Docs WG rejuvenation (Andrew Myers)
   4. Add agenda items here
3. Moderator & notetaker for next time
   
   1. Moderator:
   2. Notetaker:
4. After call, this week's notetaker should create the agenda for the next call:

   1. Open template agenda titled "Samvera Tech Call 2019-xx-xx"

   2. Click on ... in the top right corner, and select copy.
   3. Popup will open for location. It should contain: 
      1. Space: Samvera
      2. Parent page: 2019
   4. Select copy. New page should be created.
   5. Modify the title to remove "copy of", update it with the next date, add moderator, notetaker, and any carry-over agenda info. Click Publish.
5. PR Review
   
   1. Review issues:
   2. PR review coordinator for next time: 

Notes

hydra-pcdm

Don't remember if it was direct ancestors or one removed, add a Collection as an ancestor and as a descendent

This bypassed validation functionality

This might have been introduced with the inversion of certain predicates for membership

Is this a Hydra PCDM implementation question?

Hydra PCDM did block this from happening, so this decision was made

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 specification itself says that it is valid

LaRita: Has no strong feelings

LaRita is fine with closing it

Tagging Lynette on the issue needed, and then move to close the issue

Samvera Connect 2019 and the Developer Congress

Richard provided a "Companion Events" link to the Developer Congress page on the Confluence

Organizers should still announce the Developer Congress to the tech. mailing list

Also, listing the organizers on the page would be best

Richard emphasized that we clarify that this is not a part of Samvera Connect 2019, and that this is a separate event

Trey will draft the e-mail

Point of contact for those who are interested in participating?

Just list the Slack Channel as the primary mechanism for contact

Chris, Tom, and LaRita were the original volunteers for organizing the event

Adding the names as organizers to the e-mail will be addressed