...

Day 2:

...

In-depth discussion

Minutes from discussions

Minutes from discussions

 I -- Specific searches people might like to have exposed in Fedora

Traversing a graph -- getting stuff that's one step away from a resource. This sounds like a sparql query -- two use cases, one based on path, and the other based on date or date range, and response is always a list of uris

Give me all the children of a resource where x property matches in one way or another y value.

Give me all children underneath a resource .. as well as 404 or 405s or 410s, information on the lost resources.

Let me filter the attributes returned. A search returns hundreds but we're only interested in a few. No, clients can't define set of attributes you get back (server attributes and user attributes, clients can specify that they do not want server attributes, but can't manage either list of attributes).

We'd like some very basic counts of things: how many resources are in Fedora in order to compare with what's in the triple store or solr -- we don't have a way to get that, and Fedora is the canonical resource
We'd like quick snapshots of how many binaries vs non-binaries in the repo, the size of binaries .. how many of each RDF type, how many are there in general, etc.. You can do this with LDPath but that will hit every resource, which is a memory hit and not really what is needed.

II -- APIX

(There is a youtube video - marketing-focused; how requests are intercepted, two models for doing so).
On the gihub repo there are dockr containers and steps for getting it up and running and providing feedback.

APIX is an interface to Fedora, with methods for lots of things apps commonly want to do (processing of binaries with ImageMagick or FITS). Apps talk to APIX and it does one of two things: passes data to a service to do something, then puts data in Fedora and then sends back response, or puts something into Fedora and then passes something off to a service and then sends response.

III -- ACLs ... many get created, but does community know much about how and what implications are?

IV -- PCDM. UI might be bigger priority than community collectively realizes.

V -- Jersey is the language Fedora uses to manage REST .. Jersey is an implementation of the JAXRS specification.

VI -- Code walkthrough
  Main entry point is Fedora LDP -- there's an http module that is accessed by clients  

Other Information

Lodging

Fancy hotels near the museum:

...