Samvera Community Wiki
Samvera Tech Call 2019-06-05
How to connect: https://psu.zoom.us/j/613720745 (link will launch Zoom client – if you do not have Zoom, expand the instructions below)
Time: 9:00am PDT / Noon EDT
Moderator: @Jim Coble
Notetaker: @James Griffin
Attendees:
@Jim Coble (Duke University)
@LaRita Robinson (Notre Dame)
@Chris Colvard (Deactivated) (Indiana University)
@tamsin woo (UC Santa Barbara)
@Gordon Leacock (Univ. of Michigan)
@Collin Brittle (Emory)
@Thomas Scherz (University of Cincinnati)
Jen Diamond (UCLA)
Agenda
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)
Pre-Samvera Connect Developer Congress?
Space available for a developer get-together on the Monday before Connect 2019 in St Louis (Monday 21st October)
Same time as the Samvera Partners' meeting and the day prior to the Tuesday Connect workshops
Connect planning team needs to know before the end of July
Add agenda items here
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
Pre-Samvera Connect Developer Congress
Should a congress be hosted on the Monday before Samvera Connect?
It is the day prior to the workshops
This needs to be determined by the end of July
Tom Johnson: Informed Richard Green that this should happen
Would really like to be able to delegate planning this to members of the community
Hence, this is definitely going to be held
What else needs to be addressed?
We should provide those involved with Planning Committee that this should be held
Chris Colvard (tentatively), LaRita Robinson, and James Griffin will help with planning for this with Tom Johnson
Jim Coble: Will respond to the Planning Committee and forward these names
Hyrax on Wings
Update from Tom Johnson
Wings is the coy codename for the current effort to move Hyrax towards using Valkyrie
Last Friday, wrapped up third of four planned sprints on that planned work
There has been increasingly complete ActiveFedora adapter work in the "lib/wings" directory
In less than two weeks, there will be the final sprint
Existing ActiveFedora calls can be swapped for Valkyrie method calls
Tom is presently working to get the base Actor#save method to function properly with Valkyrie
Refactors to make peripheral ActiveFedora dependencies optional and less prominent is being addressed
Wrappers in the Hyrax code base for other functionality unrelated to persistence
The week after the next, there will be the final sprint
There may be some new participants in the last planned sprint
Hence, there might need to be some time paid to onboarding
While this is the last planned sprint, the work being addressed might not be completed
Questions
Chris: Is Valkyrie support going to be in Hyrax 3.0
Tom: There is no effort to make this happen
Overlapping with the last Valkyrie sprint, there is a Hyrax WG sprint beginning Monday
Hopefully that should lead to release candidates, which leads to a stable 3.0.0 release
Hyrax 4.0.0 will likely become a focus after 3.0.0 is released
3.0.0 will not be delayed for the Valkyrie support work to be completed
Samvera is not managing releases from the standpoint that big features come with *.0 releases
Contrary to this, non-breaking features should become more commonplace
Next Scheduled Call
Chris: Moderator
Thomas Scherz: Notetaker
Tech. Call concluded at 09:17PDT/12:17EDT
Hyrax Pull Request Review
Led by Chris Colvard
3772
Labeled as in progress, but it should not be
Addresses issues for specifying the height and width for the IIIF Manifest consumed by the Universal Viewer
The Universal Viewer is still going to remain a fixed size on the page
Approval requested
3776
This has not had any review yet
Relates to "featured works" within the Hyrax UI
Seems fine to Tom Johnson
Chris will add Jen Diamond to the group of reviewers for Hyrax
3764
Is this a good PR to leave for the Working Group?
It's a reasonable substantial change, and it requires more sustained review
Chris Colvard requested himself for review
James needs to get the BE PRs updated and rebased
3560
Reviewed a while ago and asked for some additional changes
This might just need a rebase at this point
Do we wait and let them pick it back up?
It's going to be closed by StaleBot tomorrow if it does not get updated
3528
Definitely not a work in progress
Chris requested some tests, and Rob Kaufman did not introduce these
Is this desired for a 3.0.0 release?
Tom: Not really sure if this is a 3.0.0 blocker
This is also going to be closed by StaleBot tomorrow
3543
Confirmation for moving between tabs in collection editing interface
There was a change pushed after tests were requested
StaleBot will close this in three days
This is a Hyrax WG item
3762
Inform the user that they cannot make themselves a proxy user
This will be closed in four days
Chris reviewed this, but left it due to some confusion surrounding the behavior
Will delegate this to the Hyrax WG
3293
Introduces significant metadata changes
This cannot be shipped until there is a migration strategy for this
Tom: Might be able to coach the committer through next week
3716
GeoNames integration
Lynette was going to work with the assignee
3760
Julie wanted to finish this by the end of the week
UniversalViewer and alpha channels
Feels like this is a substantial change
Rob performed a review
Tom: This should just need a rebase, and then Tom can also review it
It should also be squashed, there are questionable commit names
Chris: The dependency upon Riiif within the CharacterizeJob seemed questionable
Tom: Agreed, Riiif is an optional dependency in Hyrax, so this might be a problem
Better to inline the Modules that this PR depends upon
Hyrax PR evaluation completed for this week
Are there any Samvera repository PRs aside from those for Hyrax which require some review?
(Nothing was identified)
Session concluded at 09:37PDT/12:37EDT