You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/share-on-ogm.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -77,15 +77,15 @@ A hashed directory structure makes it easy to include additional materials and d
77
77
```
78
78
79
79
!!! note
80
-
80
+
81
81
Institutions may choose to use a combination of structures, such as hashed directories within categorical folders.
82
82
83
83
84
84
## 4. Determine file names
85
85
86
86
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.
87
87
88
-
### 1. Naming by item ID
88
+
### Naming by item ID
89
89
90
90
91
91
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
100
100
...
101
101
```
102
102
103
-
### 2. Naming by metadata standard
103
+
### Naming by metadata standard
104
104
105
105
106
106
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