You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 17 Next »

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. Peter Winckles 
  3. Jared Whiklo (star)
  4. Ben Pennell
  5. David Wilcox 
  6. Peter Eichman 
  7. Daniel Lamb 
  8. Ben Cail 
  9. Andrew Woods
  10. Michael Ritter
  11. Thomas Bernhart

Agenda

  1. Announcements
    1.  Sprint will start on this Monday 
      1. 7 Participants
      2. 1 week + :  Jan 27- 31
    2. Fedora 6 documentation space: Fedora 6.x Documentation
      1. Updates/Corrections would be helpful... from top to bottom!
    3. Draft Fedora 6 test plan
      1. Feedback welcome!
  2. Sprint Kickoff
    1. PRs to close today or Friday:
      1. Return Identifiers from Create:  https://github.com/fcrepo4/fcrepo4/pull/1607
      2. Stage object sessions in their own directories: https://github.com/fcrepo4/fcrepo4/pull/1606 
      3. Get Resource Service: https://github.com/fcrepo4/fcrepo4/pull/1608
    2. Housekeeping to be done right away:
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.

      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    3. Cross cutting concerns
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      7. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    4. CRUD Binary
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    5. CRUD RDF
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    6. Containment
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    7. Migration Utils
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
  3. Decisions and Open Questions
    1. Where do we stand regarding Identifiers?
      1. Identifiers, RDF and Import Proposal
      2. Fcrepo6 Resource Identifiers
  4. Import Export Bag Profile
    1. Beyond The Repository grant produced a new bag profile
    2. Adding support to export and import in said profile
  1. Pair tree  testing partner
  2. <Your topic here>

Tickets

Full list of Fedora 6.0.0 Unclosed

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.

  1. 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.

  2. 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.

  3. 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.

  4. 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.

Notes

  1. Sprint starting next week. 7 participants.
  2. Fedora 6 documentation is up and ready to be reviewed/edited to remove Modeshape references or add OCFL stuff.
  3. Technology Sub-group of Fedora Leaders working on a Fedora 6 Test plan. This is a general plan of things which we want to test. Some of this will be dealt with internally (to development) and others might require requesting support from the community. If you have any thoughts of what we should be testing before we present it to the community. This is currently a brainstorming task, so add any thoughts we can review/revise later.
  4. Sprint planning, this is only a 1 week sprint
    1. 3 PRs to be reviewed, Danny to look at 1606 & 1608. Ben Pennell to look at one or more of these as well.
    2. Any concerns with any of the tickets that might require more thought/discussion.
    3. Priorities are:
      1. Read/Write binaries
      2. Implement containment index (including some simple Archival Group)
      3. Bring migration-utils up to speed.
    4. Lots of tickets around CRUD-related processes that are small and well scoped.
    5. State tokens - Do we order the RDF to allow for a checksum/fixity check? State token only needs to reflect the fact that a resource has/has not changed. i.e. last modified date. Fixity would be a much higher bar, but a great add.
    6. Tombstones - not currently being handled, this is likely to be larger task and will tie in with the other delete tickets
    7. Containment index - Peter will pick up where he left off.
    8. This meeting was the sprint planning meeting, so we will not try to do a kickoff next week.
    9. Focusing on the binary and containment sections would be the critical objectives for this sprint.
      1. Goal, create and retrieve binaries
      2. Goal, demonstrate containment - should be able to nest a resource inside another resource, whether it be a container in another, or binary in another. Not necessarily AGs.
    10. Danny may go through and tag priority
    11. Migration util goals for the sprint?
      1. Ben Cail - what its already doing is good with him. Might be helpful if he could run against a large set to test scale during the sprint
      2. Thomas - Will take time to run the tests on a large F3 repo. Keeping it aligned with f6 expectations.
  5. What is the current understanding around what Fedora is expecting for identifiers.
    1. Perhaps part of this sprint is moving the above linked Google docs decisions to a wiki page for more formality. Disambiguation is another part that has to be done (FCREPO-3139)
  6. BagIt Profiles
    1. Mike Ritter - Starting work on stuff from the "Beyond the Repository" grant
      1. New bag profile with the import/export tool
      2. Rosie from Emory is interested in using this profile, glad to know that someone else is looking to implement it.
      3. Does not add much beyond the base profile, in part because some components were added to the canonical profile.
      4. Time frame - already pretty far along

Actions

  • Clarify in in documentation that multiple simultaneous writes to OCFL are not supported



  • No labels