Versions Compared

Old Version 6

changes.mady.by.user Danny Bernstein

Saved on

compared with

New Version Current

changes.mady.by.user David Wilcox

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Danny Bernstein
  2. Jared Whiklo 
  3. Andrew Woods 
  4. Peter Winckles  
  5. David Wilcox (star) 
  6. Ben Cail
  7. Thomas Bernhart 
  8. Daniel Lamb
  9. Ben Pennell

Agenda

  1. Announcements

    1. PRs closed this last week:
      1. (no JIRA): https://github.com/fcrepo4/fcrepo4/pull/1662 Ben Pennell
      2. (no JIRA): https://github.com/fcrepo4/fcrepo4/pull/1663 Peter Winckles
      3. (no JIRA): https://github.com/fcrepo4/fcrepo4/pull/1665 Peter Winckles
      4. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-3278
         Jared Whiklo
    2. New tickets/bugs: 
      1. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-3280
      2. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-3281
  2. Committers leaders call upshot
  3. Containment Index
    1. How to handle SQL differences (H2, MySQL, PostgreSQL) - pluggable connectors?
  4. (5 mins)
    1. Follow-on meeting next Wed @11am ET - 2020-04-29 - Fedora Leaders - Committers Meeting
    Fedora 6 testing
  5. fcrepo4-docker and fcrepo-docker status updateOpen PRs
  6. Pre-Sprint focus:
    1. simple search plan
      1. What do we plan to support in 6.0.0? 
      2. 2019-02 Fedora Design Summary#201902FedoraDesignSummary-Queryservice.1Summary
      3. Query Service Specification
      4. Samvera / Valkyrie Queries
  7. Fedora 6 testing
  8. Containment Index
    1. How to handle SQL differences (H2, MySQL, PostgreSQL) - pluggable connectors?
  9. Housekeeping PRs
    1. https://github.com/fcrepo4-labs/fcrepo4-docker/pull/38
    2. https://docsgithub.google.com/documentfcrepo4/d/13C_UhB37docTd8ZTD1ZSKuFhX6q9_3Boo67hjUC2YyM/edit?pli=1fcrepo4/pull/1628 
  10. Fedora 6 Roadmap?

  11. <Add your topic here>

    Expand
    titleTickets resolved this week...

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


...

  1. In Review

    Expand

    Jira
    serverDuraSpace JIRA
    jqlQueryfilter=13100
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  2. Please squash a bug!

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13122
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  3. Tickets resolved this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13111
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


  4. Tickets created this week:

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=13029
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5


Notes

Announcements

  1. Lots of good work happening this week
  2. New bug tickets
    1. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3280
    2. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-3281
      1. Andrew used git-bisect to pin down the error
      2. Getting the build to work with IntelliJ

Leaders/Committers Call

  1. Follow-up meeting scheduled for next Wednesday
  2. Setting context for vanilla-rebuild functionality
    1. Supporting both plain OCFL and Fedora-specific OCFL for read/write, rebuild, etc. would be challenging
    2. If Fedora leaves Fedora-specific data in OCFL directories this might be unexpected/unwanted behaviour
      1. However, this extra data could be stored in a .fcrepo directory which would be fairly easy to remove if desired
      2. The .fcrepo directory may actually be useful for providing context of the previous state of the resources within a Fedora repository
      3. Reaction from OCFL editors: why now use the extensions directory?
        1. Put .fcrepo inside extensions outside the context of the OCFL Object
        2. Risks complexity, splitting metadata in different locations
    3. Fedora should be able to import and read vanilla OCFL without adding specific Fedora data
      1. Fedora would add Fedora-specific data in order to manage/write to the content on disk
      2. Documentation should be clear about what operations on vanilla OCFL objects do and do not add Fedora-specific data
  3. Fedora makes assumptions in the absence of specified details based on the platform needs. It seems like there are multiple categories of info that are relevant to different purposes, such as:
    1. common to ocfl objects (timestamps, a checksum, etc),
    2. useful for a linked data platform (interaction models, containment),
    3. fedora specific (external binary location, binary details, creator/modifier details),
    4. user provided RDF/binary content.
  4. In the last design document, all of those details were going into .fcrepo except for the last one. Some can be derivable, some only matter in some contexts
  5. Proposal: Fedora doesn't know how to upgrade from read-only vanilla OCFL. Upgrading to read/write would require a migration utility
    1. In this case the repository would be in read-only mode - can't create new resources without running the migration utility
    2. Migration would be in-place - adding new versions with Fedora-data
  6. Two different concerns: software maintainability vs. long-term preservation
  7. Ben C: Desire for basic read/write HTTP layer over OCFL
    1. Doesn't want .fcrepo directory

Fedora Docker Implementation

  1. Updated to Fedora 5.1.0, fixed some issues
  2. When/how are Fedora snapshots pushed to the Maven repository?
    1. Every GitHub commit triggers Jenkins. Successful builds result in Sonatype snapshots
      1. This is currently broken but should be fixed soon
    2. It would make sense to trigger the Docker pipeline as part of the Travis workflow once Travis has been configured to publish snapshots

Actions

  •  Danny Bernstein to ensure that a JIRA exists for scenario of transaction does not succeed completely, but rollback does succeed (see: 2020-04-23 - Fedora Tech Meeting)
  •  Ben Pennell to create ticket to use OCFL optimistic locking in transactions (see: 2020-04-23 - Fedora Tech Meeting)
    Jira
    serverDuraSpace JIRA
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
    keyFCREPO-3271
  •  Peter Winckles to create a JIRA to investigate support for optimistic locking and mutable head (see: 2020-04-23 - Fedora Tech Meeting)
  •  Who:  Clarify in documentation that multiple simultaneous writes to OCFL are not supported
  •   Who:  After team has a chance to comment, send Ghost Node idea to general community for feedback
  •   Who: Decide who works on what in the next sprint

...