| Coverage
data (1) |
|
|
|
|
|
|
|
|
|
|
|
|
| ERM requires a
holdings / coverage schema |
|||||||||||
| that is: |
|||||||||||
| ® | Rich enough to accommodate
"routine" |
||||||||||
| irregularities
(supplements, indexes, unusual |
|||||||||||
| numbering and
chronologies) |
|||||||||||
| ® | Simple enough to facilitate easy
production and |
||||||||||
| common adoption
by libraries and vendors |
|||||||||||
| ® | Interoperable
with schemas in existing systems |
||||||||||
| Current
standards and methods seem to be either |
|||||||||||
| rich or simple,
but not both |
|||||||||||