Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated notes

...

  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

The participants that decided to cancel the second tech meeting from today will be cancelled, as there is an ongoing sprint.

  1. Highlights from last week:
  2. preparations for Tomorrow's meeting between Fedora and OCFL team regarding possibly large inentory files in OCFL takes place tomorrow
    1. regarding fedora implementation of OCFL persistency: no decission has been made so far regarding unversioned content/modifiable head
    2. Idea from Andrew Woods: instead of writing new OCFL version for every change, write all changes to head until explicit Fedora version is created
      1. would mean OCFL versions and Fedora versions are aligned again
      2. no head version, treat latest version as head (no extra directories)
      3. squashing would be possible
      4. Peter Winckles : with this approach it could get tricky to implement updates as atomic operation (create v1, copy to v2, write update to v2); but approach could work
      5. Fedora Leaders and OCFL editors must be contacted to check if this approach is feasable
    3. Do we need to support deleting of mementos if we implement a squashable HEAD?
  3. Sprint Update:
    1. design discussions
      1. Presentation of Flow Diagram Adding Binary to Existing AG by Ben Pennell
    2. core development gateway tickets
      1. FCREPO-3046: should be done later this day(?)
      2. Review of https://github.com/fcrepo/fcrepo-specification-atomic-operations/pull/8
        1. no need to limit transactions to single resources
        2. keep a lot of existing approach for transactions if possible

Actions

...