en:user:metadata
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
— | en:user:metadata [2023/03/13 01:46] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | |||
+ | |||
+ | ====== Metadata in Greenstone ====== | ||
+ | |||
+ | Metadata is data about data. In Greenstone this is information about the documents, that may be separate from the content of the document -- typically title, author, creation date, and so on. | ||
+ | Adding metadata to documents is an extremely important part of building digital collections. Metadata can help users navigate collections and find the information/ | ||
+ | |||
+ | =====Adding Metadata Using GLI===== | ||
+ | |||
+ | The easiest way to add metadata is using the [[en: | ||
+ | In GLI, you create or open a collection, add documents to it, and add metadata to the documents. | ||
+ | The [[en: | ||
+ | |||
+ | |||
+ | ===== Metadata Sets ===== | ||
+ | All metadata fields in Greenstone belong to a //metadata set//, which is simply a pre-defined collection of metadata fields. Because sets will often have metadata fields with the same name (for instance, most sets will have a ' | ||
+ | |||
+ | The default metadata sets for new collections are Dublin Core (dc), the Greenstone Metadata Set (gs), and the Extracted Greenstone Metadata Set (ex). The **Extracted set** is unique because it contains metadata automatically generated during the collection building process and cannot be edited. Metadata values in this set cannot be modified (as it is extracted from the documents themselves), | ||
+ | |||
+ | The [[en: | ||
+ | |||
+ | ===== Metadata database files ===== | ||
+ | You may have metadata for your documents that is not in Greenstone metadata.xml form, for example, in MARC, OAI, or CSV (which can be created from a spreadsheet) format. This metadata has to be processed by Greenstone first before the metadata can be associated with the documents in your collection. There are several different options for processing these metadata files, depending on whether you want to be able to view and/or edit the metadata in the GLI. You can read more about these different options on the [[en: | ||
+ | |||
+ | |||
+ | ===== Greenstone archive format ===== | ||
+ | During collection " | ||
+ | |||
+ | ===== Using metadata ===== | ||
+ | |||
+ | You can make the most of the metadata you've added to your collection by using it in several different ways. You can create [[en: | ||
+ | |||
+ | <tabbox Greenstone3> | ||
+ | For example, if you want to display the value of '' | ||
+ | |||
+ | <code xml> | ||
+ | < | ||
+ | </ | ||
+ | <tabbox Greenstone2> | ||
+ | For example, if you want to display the value of '' | ||
+ | |||
+ | <code xml> | ||
+ | [dc.Title] | ||
+ | </ | ||
+ | </ | ||
+ | |||
+ | ===== Exporting metadata ===== | ||
+ | | ||
+ | |||
+ | To export a collection, open the " | ||
+ | |||
+ | There are other options specific to the various formats. You can specify XSLT files which will be applied to the resulting XML document(s) in order to customize the output format. Exporting to MARCXML uses a mapping file to map Greenstone metadata to MARC fields. The default mapping file maps only Dublin Core metadata. You can specify a custom mapping file to be used instead. Visit the [[en: | ||
+ | |||
+ | |||
+ | |||
+ | ===== Additional resources ===== | ||
+ | * **[[en: | ||
+ | * **[[en: | ||
+ | * **[[en: | ||
+ | * **[[en: | ||
+ | * The following are some unique things people have done with metadata in Greenstone: | ||
+ | * [[en: | ||
+ | * [[en: | ||
+ | * [[en: | ||
+ | * [[en: |
en/user/metadata.txt · Last modified: 2023/03/13 01:46 by 127.0.0.1