Versions Compared

Old Version 2

changes.mady.by.user Danny Bernstein

Saved on

compared with

New Version Current

changes.mady.by.user Danny Bernstein

Saved on

Key

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

...

  1. Danny Bernstein
  2. Andrew Woods
  3. Aaron Birkland 
  4. Bethany Seeger 
  5. David Wilcox (star)
  6. Ben Pennell
  7. James Silas Creel
  8. Jared Whiklo
  9. Jon Roby
  10. Peter Eichman

Agenda

  1. Announcements

    1. 5.0.1 Release
    2. Publishing CTS Test  Results
      1. https://fedora.info/spec-tests/
      2. https://github.com/fcrepo/fedora.info
    Follow up from two meetings ago: 
    1. UMD is storing checks and results for fixity checks inside Fedora, it would be good to capture this process in the community documentation.
  2. James Silas Creel 's demo of TAMU's CAP frontend for Fedora (15 minutes)
  3. Status of ecosystem tools:
    1. Java Client Release
    2. fcrepo-camel
    3. camel toolbox
  4. 5.1.0
    1. Ready for review
    5.1.0

    Archiving following GitHub projects (making read-only)

    1. PRs
      1. https://github.com/fcrepo4/fcrepo4/pull/1501
      2. https://github.com/fcrepo4/fcrepo4/pull/1502
      3. https://github.com/fcrepo4/fcrepo4/pull/1465
      4. https://github.com/fcrepo4/fcrepo4/pull/1499
      5. https://github.com/fcrepo4/fcrepo4/pull/1504 (new)
    2. Issues that re ready for work:
      1. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-
      2937
      1. 2968
      2. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-
      2936
      1. 2971
      2. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-
      2935
  5. Status of ecosystem tools:
    1. Java Client Release
    2. fcrepo-camel
    3. camel toolbox
    4. fcrepo-mint (question: is any one using it) 
  6. 4→ 5 migration and 5 → 5 support.
    1. Next steps 
     
      1. 1889
      2. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2975
      3. "Check if metadata is available in commons.js" : 
      1. https://github.com/
      fcrepo3/trippi
    2. https://github.com/fcrepo3/fcrepo-before33
    3. https://github.com/fcrepo3/fcrepo
    4. https://github.com/fcrepo3/fcrepo-historical
    5. https://github.com/fcrepo4-archive/ff-jms-solr-indexing
    6. https://github.com/fcrepo4-archive/ff-indexer-fourstore
    7. https://github.com/fcrepo4-archive/fcrepo-jruby-admin
    8. https://github.com/fcrepo4-archive/fcrepo-triplegenerators-tei
    9. https://github.com/fcrepo4-archive/fcrepo-message-consumer
      1. fcrepo4/fcrepo4/pull/1499
    11. Issues that are ready to be worked:
      1. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2937
      2. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2936
      3. Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2935
  8. 4→ 5 migration and 5 → 5 support.
    1. Next steps 
  9. Your issue here 2019 Priorities 
  10. Modeshape replacement
    11. OCFL

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


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


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


Minutes

Announcements

  1. Talked about Ruben Verborgh's blog about making a front-end developers experience using linked data easier.  Might make a shift in the accessibility of linked data. 
  2. Andrew mentioned this making him rethink the JS we use in the front end of fedora. 
  3. Aaron Birkland talked about how they use plain old JSON in their Ember JS project at Johns Hopkins.  It worked well, but is very specific to their use case given how Ember JS works.  Aaron Coburn had been looking into designing a UI with a more general approach for linked data (maybe using React); not sure of where that went.  

...

  1. Both issues done and merged into master and 5.X
    1. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2969
    2. Jira
      serverDuraSpace JIRA
      serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
      keyFCREPO-2970

...

  1. What do we want to do for this release?  Aaron Birkland  thinks a light weight cycle for this one, given the tickets involved. Bethany Seeger and Ben Pennell  agree.
  2. Simple test page should be fine for 5.0.1 - tests: building source code, running all the tests on three platforms, CTS test, and the tests in the PR for the two issues.  Maybe a few of us could go through the page and do sanity testing.  
  3. Create RC for 5.0.1?  Yes, but how long would we have for public comment on it?   Danny Bernstein will create an RC for 5.0.1 today and we will test it for 1 week then release it. 
  4. Andrew Woods  - would like to put CTS test results for 5.0.0 and then 5.0.1 results on the Fedora page.  Need to figure out how to highlight the differences between tests as well as how to interpret the test results.  A top level page that makes it easy to navigate through results would be nice.  More on this below. 
  5. 4.7.X - need a separate conversation regarding release testing process on this branch

5.0.1 Release

  • Seems like this is ready to go
  • Ran into a security issue with a dependency but this has been patched
    • RC2 released, has already been tested by a few people
    • Still needs Linux and Windows sanity builds, Linux test suite run
    • Andrew and Bethany will build on Linux

Publishing CTS Test Results

  • We now have a home for test results: https://fedora.info/spec-tests/
  • Ideally, those with alternate implementations would run the test suite and issue a pull request to post the results: https://github.com/fcrepo/fedora.info
    • Alternatively, would the Fedora committers run the test suite instead? 
    • Agreement that we should trust implementers to run the suite and report the results

James Silas Creel 's demo of TAMU's CAP frontend for Fedora (15 minutes)

  • Needed to edit metadata in Fedora, HTML interface is not fully featured
  • Built a Curator's Admin Platform
  • Can create new IR views, import metadata schemas
  • Visually edit metadata, add fields, batch edit
    • Can restrict which metadata properties are available to add/edit
  • Available on GitHub

...

...

  1. Java Client Release - status:  what is process? Ben Pennell unsure - the client is ready for a release and can be done now.  The process has been that there isn't really a process. Since they are under 'exts' and therefore community supported, they can release when they feel it's ready. 
  2. fcrepo-camel - status: Aaron Birkland - there's a PR there. This PR makes it 5.0 ready.  Ready for review
    1. do we support 4.7 and 5.0?  Yes, we probably should make sure that 4.7 users can still use this (either via a branch or extra code to ensure it's backwards compatible). 
    2. It would be good to see how this PR behaves with 4.74 and camel tool box.  Peter Eichmanmight already be planning to test this. Ben Pennell can test it.  The process of migrating API-X to it and the camel tool box will highlight anything that's lacking and needs to be changed. 
  • TAMULib/Cap
  • Something like a middle ground between the default Fedora HTML UI and a more fully featured front-end like Islandora or Samvera

Status of Ecosystem Tools

  • Java client
  • fcrepo-camel
    • Aaron put in a pull request which is ready for review

5.1.0

  • Development driven by need
    • Some interest in state tokens
    • Bring CTS failures to zero
      • 3 issues to resolve in addition to state tokens
  • Fixing bugs
  • Fedora 4 to 5 migration path
  • Scope of Fedora 6.0 is an OCFL-compliant ModeShape replacement
    • Probably makes sense to focus more on this release than on incremental improvements

Migration tooling

  • Fedora 4 to 5 tooling
    • Should this be part of the import/export tool or a separate utility?
      • A separate tool would be less of a maintenance headache
      • Maybe bundle a separate utility into the same import/export pipeline?
      • Have we standardized the on-disk format for exports? Is this aligned with a particular version of Fedora? Could be tied to a version of the Fedora API.

Actions

Actions

  •  Danny Bernstein to write short technical summary for the  newsletter
  •  Danny Bernstein  will setup test page for 5.0.1
  •  Danny Bernstein to create 5.0.1 RC
  •  Bethany Seeger  will start page for CTS testing results  (matrix), to include explanation of test and results
  •  Andrew Woods  will start by putting up raw HTML results for CTS now, so community can have access to them. 
  •  Checking with Peter Eichmanregarding: UMD is storing checks and results for fixity checks inside Fedora, it would be good to capture this process in the community documentation.
  •  Danny Bernstein will reach out to Yinlin Chen to see about a fcrepo4-docker release with the 5.0 architecture.

...