Page tree
Skip to end of metadata
Go to start of metadata

Time/Place

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

Attendees 

Agenda

  1. Questions from DCFUG meeting about the URIs that Fedora exposes

  2. Coordinating with Samvera and Islandora community regarding API changes (Fedora 5.0.0)
    1. Who can be the points of contact from the two communities?
    2. How should the process take place?
  3. Update on status of memento/sprint 2 work
    1. What is left to be done before merging memento-versioning into master?
  4. ...
  5. Tickets In-Review

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

Ticket Summaries

  1. Please squash a bug!

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  2. Tickets resolved this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  3. Tickets created this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

Minutes

DCFUG Users Questions:

  1. Some users would like to relax the apparent requirement in modeshape to repository url is the subject of all URLs
    1. ie people would like to be able to specify their own subject URIs.
  2. Aaron Birkland:  does the upcoming memento implementation which abandons referential integrity make lifting the single subject restriction feasible?
    1. Jared Whiklo:  I don't think so.  All we are doing for memento is replacing the jcr reference with a URI. 
    2. So only the object is being updated from a jcr weak reference to a URI.
    3. Should we consider abandoning the single subject restriction  -  now would be a good time to do it.
    4. Let's raise it on the list.
  3. Does loosening the single subject restriction break RESTful crawling? 
    1. Some users of fedora 3 are maintaining the mapping on their own.
  4. Are we talking about maintaining the mapping in Fedora?  Possibly.
    1. Question drives at doubts about Fedora's strategy fro sharing URI's broadly.
    2. Most user's are not providing direct intenet access to the internet so they are using a proxy layer.
      1. API-X can do this work.
    3. It would be useful to do a write up on the strategy for permalinks.
    4. IPFS - interplanetary file system  - might be useful to look into for inspiration.
    5.  Doran from NLM will do a writeup.

Esmé Cowles will drive conversation at Samvera Connect re Fedora 5.0.0.

Having an easy to access, automatically generated one-click on GitHub would enhance Samvera's ability to test fedora 5.

Samvera will wait for a fedora 5 release candidate before looking at migration.

We should consider putting out an "Alpha" or "Preview"  as soon as the API alignment work is done for evaluation purposes.


Updates on the status of the Sprint 2 work:

Done:

  • create timemap
  • enable versioning
  • proper headers on versioned resources

Remains to be done:

  • creating mementos
  • getting listing of mementos
  • getting mementos

Requirements for merging into master:

  • create an rdf memento
  • retrieve an rdfs memento
  • list memento
  • enable versioning on a resource


There is still significant work to be done.  Danny BernsteinJared Whiklo are trying to push the work forward.  It would be good to have another sprint to wrap it up, but may not be strictly necessary.


What's going on with clustering and high availability in modeshape? 

We should not rely on single file store or single database - it would be good to clarify the strategy here.







Actions

  • Bring the proposal to disable versioning using a read-only LDPCv to the Fedora spec editors
  • Document UMD's custom authNZ Tomcat configuration (Peter Eichman)
  • No labels