Sets and tags
OAI-PMH supports a system for the creation of sub-collections that it calls "sets".
oai4courts adds database support for a less-formal system of tags. Sets are named
according to a hierarchical system that implies an equally hierarchical partitioning
of the database. Tags may be applied in any way you like.
Implementation scenarios: where does the metadata come from?
OAI-PMH repository implementations consist of request- and error-handling scripts
that draw on a relational database (RDBMS) for the metadata they deliver. In
practice, this is because implementations that relied on real-time extraction
of metadata from documents in a file tree would be unacceptably slow. So for
practical purposes the question becomes one of how the metadata finds its way
into the RDBMS, and that in turn depends on the nature of the documents themselves,
[this is mostly a placeholder for now -- unedited notes follow]
Here's what we have in mind:
This example is the identifier for the majority opinion in NY Times v. Tasini.
It breaks into
-- the scheme oai_lii should be the same for all identifiers, everywhere, and
be associated with a series of standards documents and formal xml schemas.