Differences
This shows you the differences between two versions of the page.
— | details:repeatedelements [2023/06/07 20:39] (current) – created - external edit 127.0.0.1 | ||
---|---|---|---|
Line 1: | Line 1: | ||
+ | ====== The order and grouping of related elements in RIMMF ====== | ||
+ | |||
+ | **//Needs editing//** --- // | ||
+ | |||
+ | In RIMMF, there' | ||
+ | |||
+ | But what about elements that need to have their association with other elements preserved? And in particular, how is that handled when such elements are repeated? | ||
+ | |||
+ | This particular topic leads to one of the often-mentioned issues in moving our data out of MARC, whether into some new RDA standard, or into Bibframe. Some background discussion of this issue follows. | ||
+ | |||
+ | ---- | ||
+ | \\ | ||
+ | In MARC, the content designators, | ||
+ | |||
+ | 260 ##$aLondon : | ||
+ | |||
+ | From ISBD, we know that the publisher((MARC 260 $b)) ' | ||
+ | |||
+ | Why does MARC not do this-- | ||
+ | |||
+ | 260 ##$aLondon : | ||
+ | 260 ## | ||
+ | |||
+ | --seems like a good question in 2013, but, like so much of MARC, we have to go back to the days of typing catalog cards for an explanation. | ||
+ | |||
+ | Now, switching to RDA, we also have the core elements Publisher' | ||
+ | |||
+ | Place of Publication: | ||
+ | Place of Publication: | ||
+ | Publisher' | ||
+ | Publisher' | ||
+ | Date of Publication: | ||
+ | | ||
+ | or perhaps this (if some sort of machine-based sorting was in effect): | ||
+ | |||
+ | Place of Publication: | ||
+ | Place of Publication: | ||
+ | Publisher' | ||
+ | Publisher' | ||
+ | Date of Publication: | ||
+ | | ||
+ | Neither of the above is desirable from a data point of view; we need an explicit mechanism to connect ' | ||
+ | | ||
+ | We ran into this problem very early in RIMMF development. Our solution was to apply occurrence numbers to the elements when they are created, to save this occurrence info when the record is saved, and then to follow those occurrence numbers whenever the record is reloaded. | ||
+ | |||
+ | For example, in RIMMF, the user may enter publishing information (for a pattern like the one above) in any variety of groupings. Here is one possible ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | The problem with the ' | ||
+ | |||
+ | And here is a ' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | The obvious problem we have in the ' | ||
+ | |||
+ | An additional issue we have in RIMMF is the tight contraint on elements, by default. However, it is possible to move the 'Date of Publication' | ||
+ | |||
+ | {{: | ||
+ | |||
+ | RIMMF appears to be flexible enough to save the data this way and reload it correctly. | ||
+ | |||
+ | Application developers will probably all devise their own mechanism for handling this problem. But we're not sure that is the best approach. Perhaps some new way of specifying the presentation of elements will be developed in the future, and ideally, that specification will be machine-actionable. | ||
+ | |||
+ | We believe this is an issue that needs to be discussed in more detail. | ||
+ | |||