This wiki space is archived.

The active wiki for the Samvera Community can be found here: https://samvera.atlassian.net/


Child pages
  • Samvera Tech Call 2018-03-21


This wiki space is archived. The active wiki for the Samvera Community can be found here: https://samvera.atlassian.net/

Skip to end of metadata
Go to start of metadata

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

Telephone:

Meeting ID: 613 720 745

+1 646 876 9923 (US Toll)
+1 669 900 6833 (US Toll)
+1 408 638 0968 (US Toll)
International numbers available: https://psu.zoom.us/zoomconference?m=UZ_PRwQ56TNX1pDIsdDInAu8XPVqzlX3

H.323:

Meeting ID: 613 720 745

162.255.37.11 (US West)
162.255.36.11 (US East)
221.122.88.195 (China)
115.114.131.7 (India)
213.19.144.110 (EMEA)
202.177.207.158 (Australia)
209.9.211.110 (Hong Kong)
64.211.144.160 (Brazil)
69.174.57.160 (Canada)

SIP: 613720745@zoomcrc.com

Time: 9:00am PDT / Noon EDT

Moderator: Justin Coyne

Notetaker: Chris Colvard

Attendees:

Agenda

  1. 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. Welcome all newcomers!
  2. Agenda (moderator)
    1. Call for new agenda items (moderator)
    2. Hyrax 2.1 release update
      1. Testing
      2. RC2?
      3. HELP NEEDED! Project Board
      4. Bugs requiring feedback
        1. Issue #2760 - Viewers and depositors cannot view show page of admin sets (see issue for proposed fix)
        2. Issue #2796 - Optionally hide private files
    3. Analytics Update (Nestor Walker)
      1. Status
      2. Need review for merge to master
    4. LDCX and Samvera Dev Congress
    5. add agenda item here
  3. Notetaker and moderator for next time
    1. Notes: Glen Horton
    2. Moderate: Carolyn Cole
  4. After call, this week's notetaker should create the agenda for the next call.

Notes

  1. Hyrax 2.1 release update 
    1. First round of testing done.  Need people to help fix bugs.  See Project Board for prioritized list.
    2. Bugs requiring feedback
      1. Issue #2760 - Viewers and depositors cannot view show page of admin sets (see issue for proposed fix)
        1. Admin sets didn’t have access controls before but now do because admin sets are now collections

        2. Currently admin sets listed on dashboard but can’t navigate into them due to lack of read privileges

        3. Proposal: grant access to viewers and depositors explicitly added to admin set (more details on ticket: https://github.com/samvera/hyrax/issues/2760#issuecomment-374981473)
        4. Requires migration to back fill permissions on admin sets.  This could be easily added to existing migration service.
        5. Ran out of time for discussion.  Lynette will write email to samvera-tech on this.

      2. Issue #2796 - Optionally hide private files
        1. Configuration option to toggle between existing behavior of obscured view and hide filesets the user doesn’t have access to

        2. Configurable option seems best we can do right now

        3. Is this really a blocker? Or maybe it is a new feature?
          1. No objections to removing blocker status
          2. Steve agreed on slack
  2. Analytics Update (Nestor Walker)
    1. Last week of planned sprint
    2. PR needs review for merge to master
    3. Changes include new backend code for storage of statistics and some better reporting (rest will have to be in future sprint)
    4. There was decision to store download counts locally instead of sending them to google analytics or Matomo.
    5. Is this too destabilizing to merge to master given push for 2.1 release?
      1. PR has feature toggle (off by default) to enable new functionality
      2. Should a arelease branch be cut?
        1. Would mean more work porting bug fixes between branches
        2. If a PR has already been merged to release branch then maybe it doesn't need a PR to merge to master
      3. Is there a problem with merging this to master?
        1. Needs DB migration to create new tables
        2. Hyrax 2.1 already requires DB migration so wouldn't be adding any new requirement.
      4. Lynette is nervous about anything that might slow down release.
      5. Two options: Merge into master or make a release branch
    6. Time ran out for discussion.
  3. LDCX and Samvera Dev Congress
    1. Next week
    2. Need to register for Dev Congress by end of today
    3. Agenda is on the wiki so please add your ideas: March 2018 Developer Congress Meeting Agenda
    4. No tech call next week due to LDCX.  Next call is 4/4.


  • No labels