Skip to content

Commit 7e99078

Browse files
rmseifriedrmseifried
committed
Clean up "create-metadata"
1 parent 633ac9c commit 7e99078

1 file changed

Lines changed: 12 additions & 22 deletions

File tree

‎docs/create-metadata.md‎

Lines changed: 12 additions & 22 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
1-
# Creating Metadata
1+
# Create Metadata
22
How to create metadata records in the OpenGeoMetadata schema
33

44

5-
## Authoring
5+
## Author new metadata
66

77
Step 1 of the metadata workflow is to create or collect original metadata for each layer. Depending upon the type of resource and a repository’s chosen workflows, the format of the original metadata may be in different standards or schemas.
88

@@ -16,7 +16,7 @@ The most commonly used tool for creating geospatial metadata is Esri’s ArcCata
1616

1717
**Option B: Create metadata in the OGM schema directly**
1818

19-
Other repositories skip Option A and create records directly in the OpenGeoMetadata metadata schema. Although users benefit from the more complete information that can be added to an FGDC or ISO document, these standards are not needed to run GeoBlacklight. These repositories often use a spreadsheet or a Dublin-Core-based metadata editor to create the records. Scripts can be used to convert spreadsheets (in .csv format) to JSON in the OpenGeoMetadata schema. See [Workflows and Tools](/workflows-and-tools.md) for example scripts.
19+
Other repositories skip Option A and create records directly in the OpenGeoMetadata metadata schema. Although users benefit from the more complete information that can be added to an FGDC or ISO document, these standards are not needed to run GeoBlacklight. These repositories often use a spreadsheet or a Dublin-Core-based metadata editor to create the records. Scripts can be used to convert spreadsheets (in .csv format) to JSON in the OpenGeoMetadata schema. See [Metadata Processing Scripts](../scripts) for example scripts.
2020

2121
### For resources with existing metadata files
2222

@@ -31,42 +31,32 @@ A large amount of publicly available geospatial data does not have ISO or FGDC.
3131

3232
Scanned maps from library catalogs should have MARC catalog records, and they should be able to supply the repository with metadata in the .MRC or MARC XML file format.
3333

34-
## Transforming
34+
---
35+
36+
## Transform existing metadata
3537

3638
If the metadata records are in a non-OpenGeoMetadata standard, the next step is to convert or transfer information from some or all of the fields to the OpenGeoMetadata schema. The result of this process is one or more JSON files that will be parsed and indexed by Solr. These JSON files will serve as the content to be shown in the GeoBlacklight application.
3739

3840
### Transformation workflows
3941

40-
41-
Most institutions have their own unique set of tools and workflows to perform this transformation. These workflows may differ depending on the type of item to be referenced. In most cases, automation of this process is desired, although it is possible to create the JSON files manually.
42-
43-
The process, whether automated or manual, typically involves parsing the existing metadata record, extracting the values from selected fields and inserting the value into a new JSON document under the corresponding OpenGeoMetadata schema field. In most cases the values can simply be copied over as is, although some additional formatting may be necessary.
44-
45-
See [Metadata Scripts](scripts.md) to view custom scripts and tools for additional metadata authoring techniques.
46-
4742
!!! tip
4843

49-
* The JSON files in the OpenGeoMetadata schema do not need to be stored with the data/items they are referencing.
44+
* JSON files in the OpenGeoMetadata schema do not need to be stored with the data/items they are referencing.
5045
* Multiple items can be referenced in a single JSON file.
5146
* Some fields will contain the same values for each item (e.g. `gbl_mdVersion_s`)
47+
* See [Metadata Processing Scripts](../scripts) to view custom scripts and tools for additional metadata authoring techniques.
5248

53-
### Example
54-
55-
56-
A finished metadata file could look like the following example in ISO 19139 format:
57-
58-
![ISO Metadata ](images/ISO_snippet.png)
49+
Most institutions have their own unique set of tools and workflows to perform this transformation. These workflows may differ depending on the type of item to be referenced. In most cases, automation of this process is desired, although it is possible to create the JSON files manually.
5950

60-
The process of transforming metadata from the above formats to the OpenGeoMetadata schema involves mapping or “crosswalking” fields from one format to another.
51+
The process, whether automated or manual, typically involves parsing the existing metadata record, extracting the values from selected fields and inserting the value into a new JSON document under the corresponding OpenGeoMetadata schema field. This process is called mapping or "crosswalking." In most cases the values can simply be copied over as is, although some additional formatting may be necessary.
6152

6253
![ISO to GBL Crosswalk](images/ISO-GBL.jpg)
6354

64-
65-
## Example workflow
55+
### Example
6656

6757
At Stanford, the [metadata records](https://github.com/OpenGeoMetadata/edu.stanford.purl) are natively authored in ESRI ArcCatalog and then transformed into ISO 19139. The ISO 19139 records are then transformed to MODS for the library catalog and GeoBlacklight for the [GeoBlacklight catalog](https://earthworks.stanford.edu/).
6858

6959
![Stanford Metadata Workflow](images/metadata_workflow.png)
7060
_Stanford University Metadata Workflow_
7161

72-
Take, for example, the [metadata for this layer](https://github.com/OpenGeoMetadata/edu.stanford.purl/tree/master/rf/385/pb/1942). It has the [ISO 19139](https://github.com/OpenGeoMetadata/edu.stanford.purl/blob/master/rf/385/pb/1942/iso19139.xml) version of the metadata, along with the Feature Catalog (in [ISO 19110](https://github.com/OpenGeoMetadata/edu.stanford.purl/blob/master/rf/385/pb/1942/iso19110.xml)). We also have the transformation into [MODS](https://github.com/OpenGeoMetadata/edu.stanford.purl/blob/master/rf/385/pb/1942/mods.xml) and to [GeoBlacklight](https://github.com/OpenGeoMetadata/edu.stanford.purl/blob/master/rf/385/pb/1942/geoblacklight.json), as well as a [preview image](https://github.com/OpenGeoMetadata/edu.stanford.purl/blob/master/rf/385/pb/1942/preview.jpg). In some cases, you may even have an [HTML](http://opengeometadata.stanford.edu/metadata/edu.stanford.purl/druid:rv980rt5057/iso19139.html) version of the metadata for someone to read.
62+
Take, for example, the [metadata for this layer](https://github.com/OpenGeoMetadata/edu.stanford.purl/tree/master/rf/385/pb/1942). It has the [ISO 19139](https://github.com/OpenGeoMetadata/edu.stanford.purl/blob/master/rf/385/pb/1942/iso19139.xml) version of the metadata, along with the Feature Catalog (in [ISO 19110](https://github.com/OpenGeoMetadata/edu.stanford.purl/blob/master/rf/385/pb/1942/iso19110.xml)). We also have the transformation into [MODS](https://github.com/OpenGeoMetadata/edu.stanford.purl/blob/master/rf/385/pb/1942/mods.xml) and to [GeoBlacklight](https://github.com/OpenGeoMetadata/edu.stanford.purl/blob/master/rf/385/pb/1942/geoblacklight.json), as well as a [preview image](https://github.com/OpenGeoMetadata/edu.stanford.purl/blob/master/rf/385/pb/1942/preview.jpg). In some cases, you may even have an [HTML](http://opengeometadata.stanford.edu/metadata/edu.stanford.purl/druid:rv980rt5057/iso19139.html) version of the metadata for someone to read.

0 commit comments

Comments
 (0)