Versions Compared

Key

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

...

Attendees 

Agenda

Follow from last week: 

...

Agenda

  1. Update on status of memento/sprint 2 work

    1. Remaining work
      1. creating mementos (partially complete)
        1. https://github.com/fcrepo4/fcrepo4/pull/1262 (
          Jira
          serverDuraSpace JIRA
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-2617
          )
      2. getting listing of mementos
        1. FCREPO-2623
      3. getting mementos
        1. Jira
          serverDuraSpace JIRA
          serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
          keyFCREPO-2613
           
    2. Status of Mohamed Mohideen Abdul Rasheed's in progress PR: (https://github.com/fcrepo4/fcrepo4/pull/1262)
      1. Do we need a volunteer to bring this one over the finish line? 
    3. Status of https://github.com/fcrepo4/fcrepo4/pull/1250:
      1. Support versioning with versioned child ignored
      2. Is there anything that needs to be discussed as a group in order to move this one forward? (Longshou Situ)
    4. PR's to be merged
      1.  https://github.com/fcrepo4/fcrepo4/pull/1262 (
        Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2617
        )
      2. https://github.com/fcrepo4/fcrepo4/pull/1261 (
        Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2645
        )
      3. https://github.com/fcrepo4/fcrepo4/pull/1260 (
        Jira
        serverDuraSpace JIRA
        serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5
        keyFCREPO-2621
        )'
      4. https://github.com/fcrepo4/fcrepo4/pull/1241 (just needs to be merged - all feedback it complete)
  2. Follow-up discussion from last week: 

    1. Status of Doran's write-up regarding Fedora's strategy for permalinks
    2. Abandoning the single subject restriction: any feedback/illuminating discussion on the list?
  3. ... ( please add agenda items)

  4. Tickets In-Review

    Expand

    Jira
    serverDuraSpace JIRA
    columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
    maximumIssues20
    jqlQueryfilter=14307
    serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5



...

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


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


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

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:

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? 

...


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)