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 17 Next »

Connect:

Hydra Partners Call (July 2017)
Friday, July 14, 2017
11:30 am  |  Eastern Daylight Time (New York, GMT-05:00)  |  1 hr 


Join WebEx meeting
Meeting number: 737 192 431 
Meeting password:h9cwrT45


Join from a video conferencing system or application
Dial  738605799@tufts.webex.com
Join by phone
+1-617-627-6767 US Toll
Access code: 737 192 431 

Facilitator: Dan Coughlin
Notetaker:  Mike Giarlo

EVENT RECORDING



AGENDA & NOTES

  1. Samvera Connect updates - Karen Estlund
    1. Program Committee has been formed
    2. Need program suggestions
    3. Scholarships
      1. Last year, four scholarships were offered, funded by budget surplus (registration fees).
      2. Scholarship covered registration and lodging – not travel.
        1. Rooms were provided because the hotel block had some extra rooms that could be offered to scholars
      3. Host committee cannot take on scholarships this year
      4. Would we like to continue offering scholarships?
        1. Yes!
      5. Carolyn Caizzi to follow-up with folks at Northwestern to find out about hotel block
      6. Karen to ... (sorry, missed that, kestlund – can you fill this in?)
  2. Group working on "Defining roles, responsibilities, and decision-making frameworks" - update from Mike Giarlo
  3. Valkyrie update - Trey and/or Esme
    1. Valkyrie started as an experiment to see if we could create an air gap between our front-ends and new back-end options. The experiment began because the current stack would need to be tweaked from top to bottom to accommodate this, and because Princeton has been experiencing performance problems with our stack.
    2. The Data Mapper Working Group (DMWG) was formed to bring the community in on the experiment, and their goal is to produce an MVP application using the patterns implemented in Valkyrie. The scope of the application is to be able to upload files, create collections, manage files, etc. (Trey Pendragon – can you fill these in?) – basically, the "core" functionality of a Hyrax application.
    3. Question about MVP scope
      1. Why should the MVP scope include fixity, bag import/export, and versioning?
      2. See above about "core" functionality of Hyrax. Hyrax does not provide specific fixity features, other than surfacing the result of objects' last fixity check. If you choose a backend that doesn't natively support fixity checks, e.g., PostgreSQL, it's not Valkyrie's job to invent this functionality.
      3. Same answer for bag import/export.
      4. As for versioning, Hyrax does provide the ability to upload new versions of uploaded files, and restore old versions. This has been added as an issue to Valkyrie repo. (Are we also saying it's included in MVP scope, Trey Pendragon?)
    4. DMWG has its first sprint this week. 9 people on it. Went very well.
    5. DMWG sunsetting in advance of Samvera Connect
  4. For next month's Samvera Partner call, Aug 11 ______ will take notes, and ________ will facilitate. (Ooops, missed this, Daniel Coughlin. Help?)


ATTENDEES

Add your name here



  • No labels