You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

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

    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

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.


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