An Application of OAI Sets for OLAC
In a previous
note I described a the use of OAI sets. These are essentially classes that can be applied to records. It came to mind today that in fact these classes could be used to support a variety of features that Dublin Core does not support. These classes appear in the header of the OAI Record as shown below for
<oai:header> <oai:identifier>oai:hugh4.us:0007</oai:identifier> <oai:datestamp>2023-01-07</oai:datestamp> <setSpec>LanguageSoftware<setSpec> <setSpec>Software<setSpec> </oai:header>
These classes could be used to indicate the type of record or record level metadata such as the
WEMI class of a record. Alternatively they could be used within the User Interface of the record and become part of the Application Profile supporting navigation elements. For example,
Learning Resources is not a clear bibliographic category, but could be a cross-provider class that data providers could use to support the inclusion of resources within an aggregator.
The use of OAI sets could also be used to categorize records by one of the three origional goals DATA, TOOLS, and ADVICE:
By DATA we mean any information that documents or describes a language, such as a published monograph, a computer data file, or even a shoebox full of hand-written index cards. The information could range in content from unanalyzed sound recordings to fully transcribed and annotated texts to a complete descriptive grammar. By TOOLS we mean computational resources that facilitate creating, viewing, querying, or otherwise using language data. Tools include not just software programs, but also the digital resources that the programs depend on, such as fonts, stylesheets, and document type definitions. By ADVICE we mean any information about what data sources are reliable, what tools are appropriate in a given situation, what practices to follow when creating new data, and so forth.