![]() embedding COinS in HTML renderings of Fedora objects.īy far the most flexible approach with all-around utility appears to be exposing unAPI in Fedora. ![]() Another approach would be to embed Zotero-supported metadata in disseminations, e.g. However, translators depend on regular expression matching against a site's URL, which doesn't work for the general case of supporting any Fedora based repository. Zotero IntegrationĮnabling automatic citation capture in Zotero typically involves the creation of a site translator. As a proof of concept, I also implemented an OAI-PMH resolver, designed to provide unAPI services for any application that exposes OAI-PMH. The Fedora-specific implementation discussed above is provided by an implementation of an ObjectResolver interface. ![]() It's intended to be a general purpose service, not bound to Fedora. The unAPI HTTP service is implemented as a separate web app. A more Fedora-esque solution might employ an sDef & sDep to bind against a service that generated the JSON (or RDF) array. Again, this particular implementation was an expedient. The remaining elements correspond directly to the unAPI format elements. It is simply a dissemination URI where the PID of the object is replaced with a "*". Those familiar with the Resource Index circa Fedora 2.x might be familiar with the first (inner) array element, which we called a dissemination type. A content model savvy approach might enable a dissemination that returned the unAPI formats appropriate for a given content model instance. What's called for is a programmatic means of indicating which representations of an object should be considered formats, at least as far as unAPI is concerned. Moreover, this object might be bound to services that can generate different representations of the object which wouldn't be captured at all by this approach. For example, the IMAGE datastream might just be a component in an HTML rendering of the journal article and oughtn't be considered a format on its own. However, I find this approach unsatisfactory because it doesn't allow for the author's notion of the different formats of the object. Imagine demo:1 represents a journal article and contains four datastreams, DC, RELS-EXT, XML, and IMAGE. ![]() demo:1), and consider each of its component datastreams as a format. One approach might take a Fedora digital object (e.g. There are a number of ways to implement the unAPI HTTP service. As a result, the rendering of say,, would now include those elements. For the moment, I've just modified the viewObjectProfile.xslt (located in $FEDORA_HOME/server/access/) to include these two elements. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |