...

1. Islandora/F4
2. Fedora 3 to 4 Upgration
3. Non-container LDP RDF Sources, and handling triples about non-repository subjects (see 

   Jira
   server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1361

   )
4. New JIRA tickets

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

5. ...

Minutes

1. Skipped for lack of Islandora representatives.
2. Michael Durbin: In discussion with Benjamin Armintor about Columbia's migration. Hope to learn from the experience and integrate any Columbia-sourced work into the migration tools. Tickets proceeding apace.
3. Summary by Unknown User (escowles@ucsd.edu) and A. Soroka. Three issues at play:

   1. Jira
      server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1396

      : non-LDPC LDPRs: Use cases and request were made for this by Aaron Birkland and much discussion ensued on the mailing list. Andrew Woods put the question to a committer vote, whereupon A. Soroka unleashed a veto. Now use cases are being presented and vigorously discussed, with some resolution expected soon.

   2. Jira
      server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1361

      : Arbitrary-subject triples: Mostly motivated by use cases from Aaron Birkland and Tom Johnson around managing named graphs containing arbitrary triples. General agreement that much more discussion is needed to clarify the intent and scope of this kind of change. Some community RDF/linked data experts (e.g. Rob Sanderson) have opined against this.
      1. Jared Whiklo: The triplestore was externalized in Fedora 4 because there are better triplestores out there.
   3. Server-managed triples: This is the desire to let clients of the repository control whether or not server-managed triples are in play for a given resource. There was general, if quiet, agreement that this seems like a good change to make.
4. Current tickets:
   1. A. Soroka: Java 8 related tickets: Work on Java 8 is proceeding with caution and can be tracked here:

      Jira
      server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1399

      Current expectation is that Java 8 migration will take place later this spring.
   2. Michael Durbin: Migration-related ticket

      Jira
      server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1395

      already mentioned as on plate.