LDCX at Stanford from March 23 to 25, 2015 resulted in a broad unconference agenda covering range of pertinent projects and developments in the library and museum community. Below are a few notes and take-aways that were particularly relevant to Fedora 4.
- PCDM examples
- In an effort to bring some reality and clarity to how the Portland Common Data Model (PCDM) can be applied to existing repository use cases, the following collection-types were mapped into PCDM
- Sufia / ScholarSphere - implementation of PCDM to extend Sufia Generic file capability to support complex works
- GeoHydra - implementation of PCDM for GIS
- Simple Postcard Example
- Disk Image Example
- Book
- In an effort to bring some reality and clarity to how the Portland Common Data Model (PCDM) can be applied to existing repository use cases, the following collection-types were mapped into PCDM
- PCDM JSON-LD @context
- During a session detailing JSON-LD, it was suggested that a relatively simple and straight-forward exercise of creating a JSON-LD @context for the PCDM would go a long way towards facilitating consistent usage of JSON-LD
- If you are interested in JSON-LD and/or PCDM, here is a ticket for this high-value, low-effort community contribution.
- PCDM deploying to pcdm.org with scripts
- In order to automate the deployment of the PCDM ontology based on updates to the 'master' branch, an auto-deploy setup should be established along the lines of the IIIF prior arg
- Mega-thread discussion and next steps
Server-managed triples (SMT)
SMTs should be satisfied by the existing 'Prefer' header on GET requests (Prefer: return=representation; omit="http://fedora.info/definitions/v4/repository#ServerManaged")
This should be verified under a variety of scenarios
non-repo subjects
LDPRS by client
- Look into cost of JBoss to work ModeShape ticket:
- Make clear to community that F4 does not require end of XML datastreams
- Interest in moving F4 towards Memento for versioning
