Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

Attendees 

Agenda

  1. Filesystem Federation Use Case & deprecation from core
    1. UPenn Use Case and additional info
  2. Multi-tenancy - needs from Hydra-in-a-box
  3. Fedora 4.6.0 immediately after Open Repositories?
    1. Support influx of Sufia7 users' use of JDBC over LevelDB ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )

  4. ModeShape5 towards "master" branch

    1. How do we want to move the community onto ModeShape5?

    2. Immediate need for robust migration tooling ( Unable to locate Jira server for this macro. It may be due to Application Link configuration. )

    3. Production Fedora release of ModeShape5 is pending ModeShape release 5.1.0 to include bugfix – although testing can start now!
  5. Open Repositories Tech Meeting agenda planning
    1. Preparation for All: review API Specifications
  6. Use of Maven BOMs in the fcrepo4 codebase... embrace or abort? And generally, how are dependencies managed?
  7. Commons RDF in fcrepo-kernel-api
  8. Logging recommendations and style-guide
  9. ...
  10. Status of "in-flight" tickets

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

Ticket Summaries

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

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

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

Minutes

  1. a. When people want to build infrastructure that includes Fedora 4, we recommend that people build their dependencies around Fedora 4 and implement their needs and features. We should see Fedora 4 as a specification.

    b.Welcome to join API-X to see if this fit there.

    c. F4 with MODE5 tested, file federation is continuing working.

    d. Welcome to contribute a Fedora 4 extension module, but need to maintain it continuously.

  2. There are many possible ways to implement the multitenancy feature. 
    1. See https://github.com/fcrepo4-labs/fcrepo-storage-policy
    2. Based on the request/URI and implement different storage policy
    3. Based on the mimetype or metatdata or RDF type
    4. Based on user type/roles  
  3. Some old URIs been removed /nodetype /import /export and a new important feature need to release soon so everybody can use it. If someone can review 3.A then that will be great. People now have to explicitly define their repository on json. Tell Fedora 4 to use leveldb or mysql or postgres 

  4. Moving to MODE 5 late summer. Need to finish import & export tooling.  Performace report: pqsql performance is good as leveldb and scalability is better than anything ever test.

  5. If you will go to OR16, we encourage you to attend 2016-06-13 - Open Repositories Tech Meeting

  6. No meeting next week
  • No labels

All content on the LYRASIS Wiki is licensed under the CC BY (Attribution) license, unless otherwise noted.