Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Time: 9:00am PDT / Noon EDT

Call-In Info: 1-641-715-3660, access code 651025

Moderator: Steve Van Tuyl

Notetaker: cam156

Attendees:

Agenda

  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. Welcome all newcomers!
  2. Agenda (moderator)
    1. Delete 1.0.0 tag from hyrax? (Anna)
      1. causes confusion when looking at a commit to see whether it's been released
        1. github shows that code has been released when it has not been.  This causes confusion f
      2. requires coordinated effort to not add the tag back in during future releases.
        1. Unless everyone deletes their local tags in their repos, it could get pushed back up again
        2. Add a note to the release process to either delete the local tag first or delete the remote tag again after?
      3. Here's the command to use: 
        git tag -d TagName && git push origin :refs/tags/TagName
    2. Change PCDM relationship on Collections (move from Collection hasMember Collections to Collection memberOf Collections) (Jeremy F)
      1. Rationale - performance issues along with the following:
        1. There appears to be a logical disconnect between the PCDM implementation of Collections and the validation of nesting collections:

          1. For PCDM the "parent has_member child" relationship is defined, and managed on the parent.

          2. 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.

    3. Admin Set Relationship Predicate
      1. Objects in Hyrax are currently related to Admin Sets with dcterms:isPartOf; this makes it challenging to use this generic partitive relation for other cases
        1. There is an issue discussing this at https://github.com/samvera/hyrax/issues/1461
        2. DCE would like to make the admin set relationship configurable in 2.0, advise new installers to use something other than isPartOf (what?), and change the default in 3.0.
          1. Comment here: https://github.com/samvera/hyrax/issues/1461#issuecomment-324207971
    4. Reminder to review Permission Group change proposal/notes from 2017-8-16 Samvera Tech Call
  3. Moderator/notetaker for next time (moderator)
    1. Moderator:
    2. Notetaker: 
  4. After call, this week's notetaker should create the agenda for the next call.

Notes

  • No labels