How to connect: https://notredame.zoom.us/j/94030214208 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)
Expand | ||
---|---|---|
| ||
Meeting ID: 940 3021 4208 One tap mobile
Dial by your location
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
Meeting ID: 940 3021 4208 |
Time: 9:00am PDT / Noon EDT
...
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)
- Call for new agenda items (moderator)
- Hyrax's CircleCI (and local development?) using Postgresql (Jeremy Friesen )
- Working Documents - Samvera Branch Renaming Working Group (Jeremy Friesen )
- Seeking to close call for membership on 2020-07-16
- https://github.com/samvera/hyrax/issues/4318 < last 3.0 feature
- Samvera help follow-up
- Pull request review
- 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 2020-xx-xx"
- Click on ... in the top right corner, and select copy.
- Popup will open for location. It should contain:
- Space: Samvera
- Parent page: 2020
- 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:
...
- 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)