...

1. Announcements
   1. fcrepo-migration-validator Sprint (Dec 14-18th)
   2. Alpha 2 release for next week
   3. Next meeting
   4. Fedora-related proposals for Code4Lib in March
2. Post-sprint wrap-up 
   
   1.  Sprint board
   2. Prioritized List (Red = Beta)
   3. Discussion of ticket(s):
      1. https://github.com/fcrepo/fcrepo/pull/1826
   4. Some of new tickets: 
      1. low hanging:

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

          
      2. low hanging:

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

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

      4. Documentation tickets
3. Beta
   1. Review Criteria for Beta
   2. Prioritized list of issues. (everything in red is slated for beta)
4. Pilot updates
5. <Your topic here>

Tickets

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. Announcements
   1. migration validation sprint next week - everyone's welcome
   2. release alpha2 next week, including side-loading
      1. other tickets to resolve before alpha2: 3581, 3397, 3438 (Calvin)
   3. there is a meeting next week, but not the week after
   4. code4lib - accepting talk proposals now, let David know if you want to collaborate
2. Post-sprint wrap-up
   1. https://github.com/fcrepo/fcrepo/pull/1826 - where to acquire the lock - talk w/ Peter
   2. new low-hanging fruit:
      1. 3582 - be able to choose digest algo in migration-utils (not beta-blocker, but could be helpful for migration testing)
      2. 3561 - search index - support commit() and rollback(). Or reindex any affected objects. (not beta-blocker)
      3. documentation tickets -

         Jira
         server LYRASIS JIRA jqlQuery project = FCREPO AND status in (Open, "In Progress", Reopened, "In Review", Received) AND text ~ "documentation" AND "Epic Link" in (FCREPO-3216, FCREPO-3142) ORDER BY priority DESC, updated DESC serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

3. Pilot updates
   1. validation tool will be important
   2. whitman - starting to do sample migrations
   3. deployment work - Danny will create a ticket
4. Fedora 6 Test Results
   1. Ben P suggested running them again w/ SHA-256.
5. Alpha has been released
6. Andrew Woods  and Danny Bernstein are doing a migrator validator sprint on Dec 14-18. All are welcome to join.
7. Larger leadership group call next week. Talking about criteria for beta and production release. They have a proposed list of requirements, which are needed for beta and which are for production release with an eye to available resources. Also Andrew Woods will be asking for help from leadership in moving the mutable head extension to OCFL along.
8. Things are moving along, is there any coordination on the last tickets.
9. Which tickets are more important. Spaces ticket is to encode URI when used in the RDF. To what degree characters are encoded is a question.
10. Another alpha release next week? Perhaps the week of the 14th?
11. Side-loading:
    1. How should the API look?
    2. Does resource-id/reindex make sense?
    3. Should there be a top level reindex/side loading service?
    4. Should we support a more general reindex use case or just for side-loading new objects?
       1. What are the implications for inter related objects?
12. Import statement order
    1. Import ordering differs by IDE, causing noisy PRs
    2. Create a checkstyle to enforce order
    3. Update all imports in a single PR
13. Starting F6 on migrated data
    1. Update migration utils to output to the fcrepo home directory structure (fcrepo-home/data/ocfl-root)
14. Pilots
    1. Virginia moving along mostly seeing problems related to corrupt F3 objects now

Actions