Figure The Second. We know you love technical architecture diagrams during the holidays. Although this looks a bit complicated, let’s take this apart and discuss the various parts, because it summarizes a lot of work we invested to deal with some challenging social and technical issues. This diagram is really built on three main components: the GetMyGuid service, the Triplifier Simplifier, and the Triplifier Repository. The GetMyGUID service is used to mint EZIDs that can be directly passed to biocollections managers for using at the source, or that can be associated with data in the triplestore. The Triplifier (Simplifier) is a tool for creating RDF from biocollections data, and pushing that to a user via web services or to a triplestore. We are now working out the backend architecture to deal with storing a large number of triples. We have developed this architecture to be flexible, simple, and based on understanding user needs (and concerns) with regards to permanent, unique identifiers and semantic web approaches.
Figure the Fourth. This is another “in preparation” web interface for users to get Great and Useful EZIDs. The options for doing so include pasting in a set of local identifiers, which could be set of catalog numbers or locally specific event Identifiers. The GetMyGuid service creates a second column and makes an EZID per row linked to the local identifier. A user can then import this right back into their database and have EZIDs on their source material. The “Create GUIDs” link just mints a set of EZIDs for later use. Some authentication will be required and we might put an expiration data on how long you can wait to use them. The last option is “Mint a DOI for your dataset”. You basically just type in the digital object location, and some key metadata and you get a DOI that can resolve to at least the metadata and link to the actual digital object. As always, BiSciCol will accept any well-formed, valid URI, persistent identifiers expressed by clients. We are working closely with the California Digital Library and extending their EZID API for use in this part of our project.
Summary: We end 2012 on a BiSciCol high note, and not just because the meeting was in Boulder Colorado either (because of the elevation, people! Not the legal cannabis!) We have made a lot of progress based on productive meetings, a lot of input from various folks, and a lot of time and effort by our talented staff of programmers who work so hard to develop this and also canvas the community. We should also take this opportunity to give a shout out to a new developer on the team, Tom Conlin, who is joining us as our backend database expert. Great to have him on board!
- John Deck, Rob Guralnick, Brian Stucky, Tom Conlin, and Nico Cellinese