...
The unAPI HTTP service interface defines three methods:
- listFormats (e.g.: http://www.example.org/unapi/fedora)
- listFormats for a given identifier (e.g. http://www.example.org/unapi/fedora?identifier=info:fedora/demo:1)
- getObject for a given identifier and format (e.g. http://www.example.org/unapi/fedora?identifer=info:fedora/demo:1&format=oai_dc)
The response format for 1 & 2 is an XML document that includes the name of the format, its mime-type, and an optional description of the format. For example:
...
For the moment, I've just modified the viewObjectProfile.xslt (located in $FEDORA_HOME/server/access/) to include these two elements. As a result, the rendering of say, http://www.example.org:8080/fedora/get/demo:1http://example.org/fedora/get/demo:1, would now include those elements.
...
The unAPI HTTP service is implemented as a separate web app. It's intended to be a general purpose service, not bound to Fedora. The Fedora-specific implementation discussed above is provided by an implementation of an ObjectResolver interface. As a proof of concept, I also implemented an OAI-PMH resolver, designed to provide unAPI services for any application that exposes OAI-PMH
...
One noteworthy detail: Zotero doesn't appear to parse any other format than mods, at least when using unAPI. In my server access logs, after the request for the object (e.g. http://example.org:8080/fedora/get/demo:1), the next request is for the mods format (e.g., http://example.org:8080/unapi/fedora?id=info:fedora/demo:1&format=mods). I don't see any requests for the various formats that might be available for that resource (e.g. http://example.org:8080/unapi/fedora?id=info:fedora/demo:1http://example.org/unapi/fedora?id=info:fedora/demo:1). This is using Zotero 1.0.7, I haven't tried the 1.5 preview release.
Once I added a mods datastream to my Fedora objects, browsing to an object's profile view yielded the little blue icon in my browser's location bar, indicating that Zotero could grok my Fedora object.
...