Encoding file description EAD
The encoded archival descriptionEAD is a method developed to mark the data contained by the query assistant, so that it can be queried and displayed online. Query assistant is an important resource description tool in archives and specific sets. The difference between Query assistants in different directory records is that the length, range, interpretation, and hierarchical structure are different. They usually start with a set description as a whole and describe what type of material it contains and why it is important. If this collection contains individual personal papers, there may be lengthy descriptions about this person. Query assistants to describe the number of these organizational sets-such as communications, business records, personal collections, and campaign speeches-and record results one by one from the contents of the physical boxes and folders that make up the set.
| A mods record example |
| <Mods> <titleinfo> <title> metadata demystified </title> </titleinfo> <name type = "personal"> <namepart type = "family"> brand </namepart> <namepart type = "given"> Amy </namepart> <role> <roleterm authority = "marcrelator" type = "text"> author </roleterm> </role> </ name> <typeofresource> text </typeofresource> <origininfo> <dateissued> 2003 </dateissued> <place> <placeterm type = "text"> Bethesda, MD </placeterm> </place> <publisher> NiSO press </publisher> </origininfo> <identifier type = "ISBN"> 1-880124-59-9 </identifier> </mods> |
Like the TEI Header, EAD is defined using the sgml dtd. It starts with a description of the first part of the query assistant itself (for example, who wrote it), and then continues to go to the overall description of the set and more detailed information of records or sequences in the set. If some terms already exist in the data table, you can add a pointer to the data objects. The ead dtd of version 2002 provides support for SGML and XML. By defining "Disable" only functions in SGML or "enable" only functions in XML ". The EAD standards are jointly maintained by the Library of Congress and the archives Administrators Association of the United States. EAD is popular in university libraries and history associations, as well as museums with large volumes of special data sets. Many of these data sets include unique data that is not available anywhere else, and these resources in the collection are not as readable as traditional library resources. By creating queryable EAD lookup assistants, libraries and archives can perceive their unique set in the network community.
Metadata LOM
Learning object metadataThe IEEE Learning Technology Standards Committee LTSC (Learning Technology Standards Committee) developed Lom standards (IEEE1484.12.1-2002) to enhance learning resources for technical support, such as computer-based training and distance learning, application and reuse. LOM defines the minimum set of attributes for managing, locating, and evaluating learning objects. These attributes can be divided into eight categories: ● General, containing the overall information of the object. ● Lifecycle contains metadata about object evolution. ● Technical (technical), including descriptions of special characteristics and requirements. ● Educational education includes the attributes of education/teaching. ● Copyright (Rights) describes intellectual property rights and conditions of use. ● Relation: identifies related objects. ● Annotation, including the author of comments, data, and comments. ● Classification: identifies other classification systems of objects. Each class is a layer of data elements that are assigned metadata. The example of metadata elements related to educational learning is the standard age range (typical age range), difficulty (difficulty), and standard learning time (typical learning time) of the target user) and interactivity level ). The IMS Global Learning consortium has developed a set of specifications to enhance interoperability in a learning environment. Their metadata information model is a small change based on the IEEE Lom model.
E-commerce-<indecs> and onixE-commerce-<indecs> and onix are increasingly being developed to support e-commerce applications. This <indecs> architecture (Data Interoperability in e-commerce systems) is an international cooperation effort funded by the European Commission's information 2000 Program (European Commission's INFO 2000 programme ). Collaborators are also the primary owners of intellectual property rights, such as members of publishers and record companies who want to develop a framework for metadata to support network commerce under intellectual property rights. <Indecs> the foundation of work is a data model based on the conversion of intellectual property rights and intellectual property rights. Instead of developing a new metadata mode, <indecs> tries to develop a general architecture to support/allow conversion of different modes, which is related to different formats, for example, information exchange between music, magazine papers, and books, especially those related to intellectual property rights. To support this architecture, <indecs> has developed a minimal kernel that requires metadata. Many organizations have established special metadata models based on the <indecs> architecture. There is an international standard onix (online information exchange. Onix is an XML-based metadata model developed by Book Publishers under the sponsorship of some members of the book industry transaction groups in the United States and Europe. The original onix Statute was the biggest response to online book sales and use of pictures, cover descriptions, comments, and similar information. To a large extent, books sold out of the market did not have this information. At the same time, onix for books has many elements to mark a wider range of evaluation and authorization information, as well as basic bibliography and transaction dates. Onix for a journal defines the journal product metadata in terms of titles, products, and signatures during development. When onix information is designed to be used in a publishing business cycle, it also provides some sources for the library to create a rich array of directory records. Beat (bibliographic enrichment team:
BeatProject. We are experimenting with this application. In the future, the onix metadata may also be applied to the library to create an initial bibliography record. Mappings between onix, MARC21, and unimarc for books have also been created.
