Page Comparison

AndConnect:

...

AGENDA & NOTES

1. Welcome to newcomers (1-2 min.) No roll call, but please add your name to attendees list below (at end of page). 
   Franny Gaede from the University of Oregon was welcomed to the group.
2. Facilitator and notetaker for October 13th, 2017 Call and call for future presenters (1-2 min)    
3. 1.  (Notes)  Mike Korcynski 
   2.  (Moderator) Nabeela Jaffer
4. Samvera Connect 
   1. Program Committee update - Nabeela Jaffer   The program committee is meeting bi-weekly.  61 registrations already.  There will be a registration reminder soon.  Workshops are decided.  Next step is to look at plenary and other program details.  
      
   2. Agenda & logistics for partners meeting at Connect - Steering    Notes below (through item ii.) are from Richard Green who could not attend today.    
      1. Steering have been working on assumption assumption Connect partners meeting would end at noon 
      2. Richard Green passed along 2 questions brought to his attention for discussion at partners meeting at Connect:
         1. the 2017 Samvera Annual Report – what things should be in it and who should write them?
            
         2. Spending plans – spending was put on hold during rebranding – so what would partners prioritize for Samvera and how do we ensure it happens?
            
      3. Other questions/issues that should be discussed at the Connect partners meeting?  Linda commented that governance is likely to be on the agenda.  Mike and Andrew confirmed that this is one item of a more detailed agenda for the Partners meeting to be set.)
      4. Karen commented that we should look for the email from Kristi on Sept. 6th about lodging reservations for the rooms for the extra day for the partner meeting.  Andrew commented that today may be the deadline.
      5. Chris Awre called to our attention a recent email from the Scholarship committee for Samvera Connect.
5. Short Presentation: Hyrax 2.0 highlights (10 minutes) - Michael Joseph Giarlo and Steve Van Tuyl
   1. Introduction to Hyrax (and its relationship to Sufia and CurationConcerns) (Michael Joseph Giarlo)
      Hyrax is a front end based on Samvera components supporting common repository features.   Tested on the latest Fedora 4 release.  Hyrax is often the base of a rails application.  Hyrax was born as a new gem taking its code from Sufia 7 and Curation Concerns 2, mashed together and renamed as Hyrax.  It represents a convergence of a number of solutions, Sufia, Curation Concerns, Worthwhile and Curate.  The architecture working group held a session at Hydra Connect last year to discuss the proposal for the merge of Sufia and Curation Concerns.  The boundaries between Sufia and Curation Concerns were becoming blurry and difficult for developers to navigate and it made sense to combine.    We've been working on Hyrax since last year's Hydra Connect meeting in Boston.  Hyrax 1.0 was a platform providing a path for Sufia migrations.  Hyrax 2.0 is for new adopters. 
   2. What's in Hyrax 2.0.0? (Michael Joseph Giarlo)
      
      1. Consolidated user and admin dashboards into a single, collapsible dashboard, including new functionality to: 
         1. Change site colors via dashboard settings UI 
         2. Customize About, Help, Terms, and Agreement pages in an in-browser editor 
      2. Translated user interface into five new languages: German, French, Italian, Portuguese, and Chinese (adding to English and Spanish) 
      3. Added embargo and lease management views 
      4. Disentangled licenses from rights statements, making rights statements a required field by default 
      5. Moved editable content blocks from homepage into dashboard settings UI 
      6. Improved ingest job pipeline, now agnostic with regard to whether ingest is happening in a single-filesystem context or a multi-node/cloud context 
      7. Improved support for nested data structures and controlled vocabularies in metadata fields, connecting GeoNames to the Location field and persisting both labels and URIs 
      8. Added a new background job for invoking the Fedora import-export tool 
      9. Granted all administrative users the ability to manage all administrative sets 
   3. Hyrax 2.0.0 testing plan and how to help (Steve Van Tuyl)
      The new repository managers interest group has taken over the testing of Hyrax 2.0.0.  A shared instance of Hyrax is being hosted by DCE and provides a common place for those who are curious to look at it, and it is a common place for group testing.  
      The repository managers interest group plans to also release documentation with each new release.  
      Testing will happen across several browsers and  operating systems and accessibility testing is being added.
      The documentation from the Repository Managers group about UI and Repository management may be added to the documentation home started by the documentation working group.
   4. Hyrax 2.x roadmap preview (Steve Van Tuyl)
      Collections Extensions (formerly display sets).  This work is ongoing currently.
      The analytics working group is planning development cycles.
      Tighten up group and role management features.
      Hoping to backport some of the HyKu UI features into Hyrax.
      Watch for calls for time from developers to help with this roadmap.
   5. Michael Joseph Giarlo recently sent out a Hyrax usage survey to all the community lists.  Mike has sent this out annually around August or September so that he collects results around Connect.  Please respond to the survey if you use or plan to use Hyku or Hyrax or Sufia or Curation Concerns.  Mike will present the results in a lighting talk at Samvera Connect.
6. FYI  – more reaction from the announcement of the acquisition of bepress by Elsevier:
   1. SPARC and COAR issued a joint statement indicating it underscores https://sparcopen.org/news/2017/elsevier-acquisition-highlights-the-need-for-community-based-scholarly-communication-infrastructure/ 
   2. which generated a proposal being discussed on the SPARC listserv thread called the "2.5% Commitment,"  calling on academic libraries to support several initiatives (through a "United Way like organization that would receive contributions and distribute them"):
   3. "This common infrastructure can be defined broadly but it would include at least contributions to: projects like DSpace, Fedora, Hyku, Open Journal System, ArchivesSpace or Islandora... "
   4. Since the proposal in development " is licensed under a Creative Commons Attribution 4.0 International license" it's attached below
   5. Andrew commented that this is well worth discussing at Samvera Connect.  It could change how libraries want to fund Samvera.  
   6. Rick commented that he's part of the Next Generation Repositories group mentioned in the blog post.  This group is trying to move repository resources toward consumable services.  This is still an abstract notion.  
7. Other news/items
   1. Call for Participation in Samvera EZID to DataCite DOI Working Group - Rick Johnson    EZID membership for those not part of the California Digital Library system will be sunsetted by the end of 2018, but these users will be migrated to DataCite members.  It seemed that it would be most efficient for us to pull our efforts together to address DOIs in Hyrax and elsewhere.  Rick sent an announcement to the elists earlier today.  Adopters already using DataCite and not using EZID should also participate to help us standardize around common solutions.  
   2. Call for comments on the Samvera Governance white paper - newmanld - see email from evviva sent on September 6 to all elists.  Quoting from this email:

      This group has drafted a whitepaper that covers:

      • A characterization of Samvera’s current community model (its affordances and shortcomings), including an accountability matrix
      • A shared vision of improvements we can make upon our current model
      • Four example models in use by other communities

      Note that there is no endorsement of any particular model by the group, and certain aspects of each model, including the existing one, may be advantageous; we are not advocating for adopting any of these models wholesale, but rather for a frank discussion of ways we might alter our current model to achieve the goals of increased sustainability and improved organization to share the community’s work-load.

      The whitepaper is available now for comment:

      https://docs.google.com/document/d/1MQtW-CBu5WsaGeSRg-5hjL0BsT8kAYc5SkxekdPJb58/edit#

      The group would now welcome comments from the community on the whitepaper. We request that comments come from individuals, not a uniform response from institutions/organizations. Please note that this is *NOT* a vote for one particular model or another!

      Please submit your comments by September 30th via this form:

      https://docs.google.com/forms/d/1IrCbzuKryxqBfm4j6N57yEql5bC5mEgBlRCT8xrDi9E/edit

      After comments have been received, the group will create a summary document which will be shared by October 15th to give everyone a chance to review it, absorb it, and discuss it in advance of Samvera Connect.

8. For next month's Samvera Partner call, October 13 Mike Korcynski will take notes, and Nabeela Jaffer will facilitate.

...