Skip to content

Commit ef095a4

Browse files
committed
clean up "share-on-ogm"
1 parent 7e99078 commit ef095a4

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

docs/share-on-ogm.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -77,15 +77,15 @@ A hashed directory structure makes it easy to include additional materials and d
7777
```
7878

7979
!!! note
80-
80+
8181
Institutions may choose to use a combination of structures, such as hashed directories within categorical folders.
8282

8383

8484
## 4. Determine file names
8585

8686
Determine the file-naming rules for your metadata. There are two main approaches to naming metadata files: naming by the item's ID or naming by the file's metadata standard.
8787

88-
### 1. Naming by item ID
88+
### Naming by item ID
8989

9090

9191
Each record has a unique filename based on the item’s ID. This allows multiple records to be stored in the same directory. See the [edu.harvard](https://github.com/OpenGeoMetadata/edu.harvard) repository for an example:
@@ -100,7 +100,7 @@ Each record has a unique filename based on the item’s ID. This allows multiple
100100
...
101101
```
102102

103-
### 2. Naming by metadata standard
103+
### Naming by metadata standard
104104

105105

106106
All records use the same filename pattern, such as `*/geoblacklight.json` or `*/fgdc.json`. This requires each layer to have its own folder.

0 commit comments

Comments
 (0)