How to connect: https://notredame.zoom.us/j/94030214208 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)

Click to view telephone/H.323/SIP connection instructions

Meeting ID: 940 3021 4208

One tap mobile

+13017158592,,94030214208# US (Germantown)
+13126266799,,94030214208# US (Chicago)

Dial by your location

+1 301 715 8592 US (Germantown)
+1 312 626 6799 US (Chicago)
+1 646 558 8656 US (New York)
+1 253 215 8782 US (Tacoma)
+1 346 248 7799 US (Houston)
+1 669 900 6833 US (San Jose)

Meeting ID: 940 3021 4208

Find your local number: https://notredame.zoom.us/u/aPls29JbL

Join by SIP 94030214208@zoomcrc.com

Join by H.323

162.255.37.11 (US West)
162.255.36.11 (US East)
115.114.131.7 (India Mumbai)
115.114.115.7 (India Hyderabad)
213.19.144.110 (EMEA)
103.122.166.55 (Australia)
64.211.144.160 (Brazil)
69.174.57.160 (Canada)
207.226.132.110 (Japan)

Meeting ID: 940 3021 4208

Time: 9:00am PDT / Noon EDT

Moderator: Jeremy Friesen

Notetaker: James Griffin

Attendees:

Jeremy Friesen (University of Notre Dame)
tamsin woo (UC Santa Barbara)
Juliet Hardesty (Indiana University)
Chris Colvard (Deactivated) (Ubiquity Press)
Collin Brittle (Emory)
Lynette Rayle (Cornell)
Alexandra Dunn (UC Santa Barbara)
Rob Kaufman (Notch8)

Agenda

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!
Agenda (moderator)
1. Call for new agenda items (moderator)
2. Hyrax's CircleCI (and local development?) using Postgresql (Jeremy Friesen )
  1. https://github.com/samvera/hyrax/pull/4397
3. Working Documents - Samvera Branch Renaming Working Group (Jeremy Friesen )
  1. Seeking to close call for membership on 2020-07-16
4. https://github.com/samvera/hyrax/issues/4318 < last 3.0 feature
5. Samvera help follow-up
6. Pull request review
  1. https://github.com/samvera/hyrax/pull/4440
Moderator & notetaker for next time
1. Moderator:
2. Notetaker:
After call, this week's notetaker should create the agenda for the next call:
1. Open template agenda titled "Samvera Tech Call 2020-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: 2020
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.
PR Review
1. Review issues:
2. PR review coordinator for next time:

Notes

Working Documents - Samvera Branch Renaming Working Group
- Jeremy will be facilitating this
- Looking to close the call for participation 07/16
Hyrax's CircleCI (and local development?) using Postgresql
- Pull request: https://github.com/samvera/hyrax/pull/4397
- Ensure that CircleCI runs PostgreSQL, test against a postgres ecosystem
- Request to review the pull request (Tom and Collin have already reviewed this)
- Collin is working to get a new release of the Samvera CircleCI Orb
  - Trying for a release which offers a URL for the postgres database
  - Currently, in Hyrax, this needs to be hard-coded into the Rails application config from the environment variables
- Jeremy will look to try and advance this for this afternoon
- Chris will look to review the PR at some point today as well
- When generating the internal_test_app, there should just be one database in the default development environment
  - If we can cut this over to postgres within this PR, then this should be the approach taken
  - (Otherwise, if multiple databases are supported, this complicates generating internal_test_app)
  - This also ensures that developers no longer need to mock SQLite interaction
- Release notes
  - Aspire to get this PR into the RC2 of Hyrax 3
https://github.com/samvera/hyrax/issues/4318
- Blocking issue for the next Hyrax 3 release
- Request to provide a strategy for resolving this
- Should we revert the change which led to this to begin with?
  - (All agreed with this)
  - It is an attempt to set up an Object which acts like it has a single title
    - Additional title field values are treated as if they are different metadata properties (which they are not)
    - It is not backwards compatible
    - There are issues with translations
    - Whether or not we want a primary title is a completely different discussion
  - We need to create a trail around the title/alternative title support, and add this to the Issue
- The request for a single title on the metadata form originated with the Metadata Interest Group
  - The goal is not to solve all of the problems called out by the IG
  - If you wish to display a single field, which value is displayed will always be non-deterministic
  - All of this is still problematic if one writes to Objects only using the Hyrax forms
    - However, if the forms destroy data on a roundtrip, then this problem arises
  - Request for hooks for dealing with i18n and translations
    - Forms should be handle the locales specified for each field
- If the title is multivalued, aren't all of the titles which aren't the first value alternative titles by default?
  - We are committed to supporting fcrepo, and hence, we cannot restrict the number of titles at the data model layer
  - Hyrax cannot destroy data fcrepo during the roundtripping of objects, and hence, these multiple titles must remain supported
  - From a bibliographic perspective, there is a different between a title translated to Finnish, and an alternative title
  - fcrepo does not support the ordering of Hyrax Object fields in any meaningful way
  - "How I filter which title I want to display on the form" is a question without an obvious answer, except in the case of translation/i18n
  - When you see multiple titles, in MODS, there is an attribute which indicates which is the primary title
    - Something like this, but in the RDF, would be extremely helpful (but is this easily implemented?)
    - "Alternative Title" is a legitimate, separate bibliographic field, and not just a subset of multiple title field values
    - "Alternative Title" was used in Hyrax was not used with the bibliographic standards in mind
      - It might be better to use a local URI predicate to store these other multiple titles
    - Hyrax cannot tell fcrepo that there cannot be more than one <dc:title>
- Tom will revert the original PR which introduced this work
  - That alone should unblock the Hyrax 3.0 release
  - Single-valued titles as a 3.1 feature seems reasonable
Next Scheduled Call
- Moderator: Tom
- Notetaker: James

Pull Request Review

https://github.com/samvera/hyrax/pull/4440
(Chris and Tom reviewed this)

Browser not supported