...

1. Announcements
   1. Sprint:  Feb 8-19
2. Thoughts on the Leaders Committers call
3. Affirming the team's understanding of famous current issues/bugs: 
   1. bloated directory from migration utility update
   2. Fedora 3 "bad" checksum issue - for reference the MOTHER OF ALL THREADS on the subject (JIRA:

      Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3604

      )
      1. Changes to migration-utils
      2. Expectations for the fcrepo-migration-validator
   3. The Daniel Lamb Bug
   4. The new Prefer Header recently accepted as part of the Fedora API  : https://github.com/fcrepo/fcrepo-specification/pull/412
      1. Implications
         1. Core: http://fedora.info/definitions/fcrepo#ServerManaged is not currently recognized
         2. Test Suite
   5. The new  resource header  (json) field jira that will make the following PR's no longer need to be merged:

      1. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3592

      2. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3591

      3. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3595

      4. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3593

      5. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3596

   6. Validation error reporting on start up and side-loading: What is going to work for the user? 
      1. For reference: https://github.com/fcrepo/fcrepo/pull/1852#pullrequestreview-577812174
4. PRs 
   1. object validation
      1. https://github.com/fcrepo/fcrepo/pull/1852 (wiring validation into fedora)
      2. https://github.com/fcrepo/fcrepo-storage-ocfl/pull/28 (validation logic)
   2. Minimum container triples: https://github.com/fcrepo/fcrepo/pull/1851
   3. ?
5. Sprint planning:
   
   1. Testing

      1. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3612

      2. https://docs.google.com/document/d/1ihoAHlnl1X8yCLF9cXT-ZmZFkCX37nYzgqIc-U3J2YQ/editPerformance Testing Criteria
   2.  Development: Are the following must haves for beta?

      1. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3610

      2. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3605

      3. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3601

      4. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3597

      5. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3584

      6. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3585

      7. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3606

   3. Documentation

...

1. In Review

   Expand
   Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

2. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

3. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

4. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

   
   

Notes

1. Affirming the team's understanding of famous current issues/bugs: 
   1. bloated directory from migration utility update
      1. Peter has offered a potential solution to Calvin - just waiting to hear back
      2. Could also be due to incorrect size being reported from du command
   2. Fedora 3 "bad" checksum issue - for reference the MOTHER OF ALL THREADS on the subject (JIRA:

      Jira
      server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3604

      )
      1. Changes to migration-utils
         1. Extract data stream from inline XML and calculate checksum based on that
      2. Expectations for the fcrepo-migration-validator
         1. Bad checksums in Fedora 3 will stay in Fedora 3 - validator will not carry this forward
      3. Danny will create JIRA tickets to track these issues
   3. The Daniel Lamb Bug
      1. Danny migrated a dataset with spaces in IDs
      2. Migration worked but updating a resource resulted in corrupted RDF with spaces in the IDs such that the object can no longer be read
      3. May be an issue with Millner
      4. Jared will help with debugging by trying to duplicate the issue
   4. The new Prefer Header recently accepted as part of the Fedora API  : https://github.com/fcrepo/fcrepo-specification/pull/412
      1. Core: http://fedora.info/definitions/fcrepo#ServerManaged is not currently recognized
         1. Danny will create a JIRA to update
         2. Do we deprecate or accept both?
            1. Add to list of breaking changes and deprecate
   5. The new  resource header  (json) field jira that will make the following PR's no longer need to be merged:

      1. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3592

      2. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3591

      3. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3595

      4. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3593

      5. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3596

   6. Validation error reporting on start up and side-loading: What is going to work for the user? 
      1. For reference: https://github.com/fcrepo/fcrepo/pull/1852#pullrequestreview-577812174
      2. Currently, on start up, log messages indicate validation failures
      3. As a user, if you don't examine the logs, you won't notice the failures - need to document clearly
2. PRs 
   1. object validation
      1. https://github.com/fcrepo/fcrepo/pull/1852 (wiring validation into fedora)
      2. https://github.com/fcrepo/fcrepo-storage-ocfl/pull/28 (validation logic)
      3. Danny will merge these today
   2. Minimum container triples: https://github.com/fcrepo/fcrepo/pull/1851
      1. Andrew is reviewing this
3. Sprint planning:
   
   1. Testing

      1. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3612

      2. https://docs.google.com/document/d/1ihoAHlnl1X8yCLF9cXT-ZmZFkCX37nYzgqIc-U3J2YQ/edit
   2.  Development: Are the following must haves for beta?

      1. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3610

      2. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3605

      3. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3601

      4. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3597

      5. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3584

      6. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3585

      7. Jira
         server LYRASIS JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-3606

   3. Documentation

Actions