Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

Attendees 

  1. Danny Bernstein  
  2. Arran Griffith  (out)
  3. Jared Whiklo (star)
  4. Peter Winckles 
  5. Ben Pennell 
  6. Calvin Xu 
  7. Michael Ritter 
  8. Demian Katz  (out)
  9. Geoff Scholl 

Agenda

  1. Announcements
    1. https://phaidracon.univie.ac.at/phaidracon-2021/day-1-november-17-2021/
    2. demo video
  2. Camel toolbox update - release is in progress
  3. Survey Results (Part 2)
  4. Scheduled fixity service
  5. New Issue:
    1. FCREPO-3792 - Getting issue details... STATUS
  6. 5.x Release Status
    1. Modeshape fork PR: https://github.com/fcrepo-exts/modeshape/pull/12
  7. PRs
  8. Progress on Tickets
    1. FCREPO-3790 - Getting issue details... STATUS
    2. FCREPO-3768 - Getting issue details... STATUS
    3. FCREPO-3751 - Getting issue details... STATUS
    4. FCREPO-3673 - Getting issue details... STATUS
    5. FCREPO-3719 - Getting issue details... STATUS
    6. FCREPO-3635 - Getting issue details... STATUS
  9. ?

Tickets

  • In Review

    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Minutes

  1. Announcements
    1. Danny was part of a roundtable for Phaidracon. Phaidra is a digital management system out of University of Vienna. 3 day conference.
    2. Demian did a demo video for the camel-toolbox http forwarding service. May not have been released yet.
    3. End of the month a Fedora workshop for Squib coming up at the end of the month.
  2. Not a huge response to the survey. Lots of interest in a scheduled fixity service.  How do we move this idea forward?
    1. Call a meeting with those interested to flesh out the proposal.
    2. Do you check only HEAD state or all past versions?
    3. For large repositories this would need to be a continous running process. But for smaller repositories we would not to perform too many checks in a small timeframe.
    4. What data do we track for a check? Is this sort of an audit service?
    5. Make use of the camel-toolbox's existing fixity service?
    6. Do we store fixity output on the resource? Do we send an email or call an external service?
      1. Storing the fixity result on the resource would generate an OCFL version which could cause OCFL bloat.
    7. Side discussion about OCFL version squashing and how it might work.
  3. PR in fcrepo-camel-toolbox that Danny needs for the release.
  4. PR for modeshape S3 issues need to create release of it.



  • No labels