Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

505 formatted contents note #184

Open
CECSpecialistI opened this issue Nov 25, 2021 · 18 comments
Open

505 formatted contents note #184

CECSpecialistI opened this issue Nov 25, 2021 · 18 comments
Assignees
@lake44me
Labels
5XX MARC fields from the 5XX spreadsheet spreadsheet section assignment issues that reflect progress and provide general discussion space for sections of mapping work
Projects
MARC21 to RDA-RDF Mapping
Milestone
MVP for Transform...

Comments

@CECSpecialistI
Copy link
Collaborator

https://github.com/uwlib-cams/MARC2RDA/blob/main/Working%20Documents/5XX.csv
@CECSpecialistI CECSpecialistI added spreadsheet section assignment issues that reflect progress and provide general discussion space for sections of mapping work 5XX MARC fields from the 5XX spreadsheet labels Nov 25, 2021
@CECSpecialistI CECSpecialistI added this to the PCC RDA BSR milestone Nov 30, 2021
@SitaKB SitaKB added the 00X MARC fields from the 00X spreadsheet label Jan 7, 2022
@CECSpecialistI CECSpecialistI removed the 00X MARC fields from the 00X spreadsheet label Jan 26, 2022
@lake44me lake44me self-assigned this Jun 1, 2022
@CECSpecialistI CECSpecialistI moved this from To do to In Progress in MARC21 to RDA-RDF Mapping Jun 15, 2022
@lake44me
Copy link
Collaborator

lake44me commented Nov 9, 2022 •
edited by CECSpecialistI

Draft special mapping for 505 * 0 subfields t and r:

For each $t [Title] in the field, mint an Expression identifier and relate it to the expression described using rdaeo:P20319 [aggregates].
For each $t Expression, mint a Work identifier and relate it using rdaeo:P20231 [has work expressed]
For each $t Work, add triple rdawd:P10088 [has title of work]; predicate is the string content of $t.
If any $t is immediately followed by $r [Statement of responsibility], add a triple for that $t Work, rdawd:P10065 [has creator agent of work], predicate is the string content of $r .
(Skip over $g. )

Potential problems with mapping:
This assumes a pattern that might not be uniform. If, for example, a chapter of a book has two authors identified in the contents, should we expect two $r subfields, or both author names in one $r as they appear in the TOC (e.g. " "John and Linda Smith"? LC's definition of the subfield seems to assume one author and one $r encompassing the "statement of responsiblity".

This is why I'm choosing the least specific relationship to an agent, without specifying person, corporate body or whatever. But, it probably is not vague enough.

rdam:P30117 "has statement of responsibilty" is available as a Manifestation element, but it is not clear that use of that relation would encompass whatever appears in a $r. It seems to point to having separate elements for individuals (and sometimes utilizing more specific roles) rather than transcribing whole whatever is contained in the manifestation source related to responsibility overall (like a 245 $c e.g. "John Aarons, Lisa Smith, and Linda Wagner". ??? It would also complicate the mapping to have to mint the Manifestation IRI if we don't have to (it's not clear that we need to, to me, yet).

@AdamSchiff
Copy link
Collaborator

AdamSchiff commented Nov 9, 2022 via email

@AdamSchiff
Copy link
Collaborator

AdamSchiff commented Nov 9, 2022 via email

@GordonDunsire
Copy link
Collaborator

There is also a problem with the first transform rule (For each $t [Title] in the field, mint an Expression identifier and relate it to the expression described using rdaeo:P20049 [aggregates]) because it confuses the manifestation being described with the expression that it embodies

This can be resolved as follows.

For each $t [Title] in 505 *0, mint an expression (IRI) and:

a) relate it to the manifestation being described using rdamo:P30139 {has expression manifested].
b) relate it to the string value of $t using rdaed:P20312 [has title of expression].

[This satisfies conformance with RDA for an expression.]

For each $t, mint a work (IRI) and:

c) relate it to the corresponding expression using rdaeo:P20231 [has work expressed].
d) relate it to the string value of $t using rdawd:P10088 [has title of work]

[This satisfies conformance with RDA for a work.]

For reasons given by @AdamSchiff, I think $r can only be transformed as a relationship, and only if no role is recorded (e.g. 'edited by'). I don't think it is possible to safely process the critical condition: how would a machine strip out role statements? However, the potential transform is:

If a $t is immediately followed by $r:

x) relate the expression minted from $t to the value of (normalized, filtered) $r using rdaed:P20301 [has related agent of expression], or using rdaed:P20053 [has creator agent of expression].

[The 'creator' relationship is viable because RDA treats the creator of a work as the creator of any expression that realizes the work (element scope note). It is not safe to map to 'has creator of work'.]

Example: transform of 'Enhanced' example in MARC 21 Bibliographic.

ex:M1 rdamo:P30139 ex:E1 .
ex:E1 rdaed:P20312 "Quark models".
ex:E1 rdaed:P20053 "J. Rosner" . // only if it can be parsed
ex:E1 rrdaeo:P20231 ex:W1 .
ex:W1 rdawd:P10088 "Quark models" .

ex:M1 rdamo:P30139 ex:E2 .
ex:E2 rdaed:P20312 "Introduction to gauge theories of the strong, weak, and electromagnetic interactions".
ex:E2 rdaed:P20053 "C. Quigg" . // only if it can be parsed
ex:E2 rdaeo:P20231 ex:W2 .
ex:W2 rdawd:P10088 "Introduction to gauge theories of the strong, weak, and electromagnetic interactions" .

etc.

@CECSpecialistI
Copy link
Collaborator Author

Skipping over $g will result in whole/part relationships between parts and chapters being lost...some $t's relate to a $g? Is that the intention? Is it inconsistently applied, so we won't know where one $g ends and another begins?

I think it's unsafe to map $r to any kind of WEMI-Agent relationship for reasons Adam and Gordon have stated. Is "statement of responsibility" an option? I can see things like "by Laura Akerman, with comments by Adam Schiff, Gordon Dunsire, and Crystal Yragui" occurring in 505 00 $r.

@lake44me
Copy link
Collaborator

@CECSpecialistI Sorry I have not had a change to dig back into this discussion this week or redo the example, but Gordon's advice is starting to sink in, particularly the part about relating the aggregated expression to the manifestation for the work as a whole (where the aggregated work is manifested).
I think the manifestation property rdam:P30117 "has statement of responsibility" could do fine for the limited purpose of providing a field that could be keyword indexed for the name keywords it probably contains. This could be distinguished from rdam:P30105 has statement of responsibility related to title proper if need be. This doesn't connect the names with the titles, nor connect the titles with their numbering or placement in the work. New cataloging might get fancier with breaking things out depending on institutional preferences, but I'd feel ok about it not being too "lossy" for the Enhanced TOCs.

I can think of more ambitious things to do to try and process this field using fancy programming, but for what we're doing now, I'd feel ok doing these mappings.

@lake44me
Copy link
Collaborator

lake44me commented Nov 29, 2022 •
edited

Latest instructions and example for enhanced 505:

For each $t, mint an IRI for an aggregated expression.
Relate the expression to the manifestation being described with rdamo:P30139 [has expression manifested].
Relate it to the string value of $t using rdaed:P20312 [has title of expression].
Mint a work IRI and relate it to the corresponding $t expression using rdaeo:P20231 [has work expressed].
Relate it to the string value of $t using rdawd:P10088 [has title of work].

Example from https://search.libraries.emory.edu/catalog/9937444781402486 Roots/Randall Goosby (New York : Decca Records, [2021] (OCoLC)on1264103732

ex:M1 rdamo:P30139 ex:AE1
ex:AE1 rdaed:P20312 "Shelter island"
ex:AE1 rdaeo:P20231 ex:AW1
ex:AW1 rdawd:P10088 "Shelter island"

ex:M1 rdamo:p30139 ex:AE3
ex:AE3 rdaed:P20312 "Porgy and Bess. Summertime ; A woman is a sometime thing ; It ain't necessarily so ; Bess you is my woman now"
ex:AE3 rdaeo:P20231 ex:AW3
ex:AW3 rdawd:P10088 "Porgy and Bess. Summertime ; A woman is a sometime thing ; It ain't necessarily so ; Bess you is my woman now"

etc.

For each $r, relate the contents to the manifestation being described using rdamd: P30117 [has statement of responsibility]

Example
ex:M1 rdamd:P30117 "Xavier Dubois Foley"
ex:M1 rdamd:P30117 "George Gershwin ; transcription by Jascha Heifetz"

@lake44me
Copy link
Collaborator

It was really tough finding an example record with an enhanced contents note. Library of Congress doesn't seem to be making them by default in their recent cataloging. I couldn't find any of the MARC21 examples in their catalog. Finally I resorted to our catalog and thought I'd have best luck with sound recordings, but had to sift through quite a few. U. of Wash. has it in their catalog too.

@lake44me lake44me moved this from In Progress to Awaiting Review in MARC21 to RDA-RDF Mapping Nov 29, 2022
@pan-zhuo
Copy link
Member

"Porgy and Bess. Summertime ; A woman is a sometime thing ; It ain't necessarily so ; Bess you is my woman now"

This looks like multiple expressions/works? Is it safe to assume one expression/work for each $t?

@GordonDunsire
Copy link
Collaborator

@lake44me's latest analysis looks good to me, but as @pan-zhuo comments it is not safe to assume that $t contains the title of only one expression/work.. In the example, it is clear that the separate titles are delimited by space-semicolon-space, and it is probably fair to assume that this is always the case; if any title has an embedded semicolon, the pattern will be semicolon-space.

@AdamSchiff
Copy link
Collaborator

AdamSchiff commented Nov 30, 2022 via email

@pan-zhuo
Copy link
Member

pan-zhuo commented Dec 1, 2022

Some more complications I could think of:

  1. Aggregates within aggregates

For example, chapter headings in an anthology. I'm unsure how useful it is to mint an aggregating expression for each chapter that is not going to cluster the individual titles within that chapter.

  1. Translated (and parallel) titles

I suppose one of the reasons we are not mapping 245$a to titles of expressions/works is that we want to avoid translated titles as expression/work titles? In practice this might create a huge number of works with translated titles as the only data point that could be used for differentiation, and I highly doubt they can be de-duped.

@CECSpecialistI
Copy link
Collaborator Author

I was thinking along the same lines Zhuo. A lot of times when I create enhanced 505 notes, there are parts with titles that aggregate chapters with titles. So, aggregates within aggregates.

@lake44me
Copy link
Collaborator

lake44me commented Dec 14, 2022 •
edited

In advance of our meeting tomorrow to decide, after viewing most of the presentations / slides from the EURIG meeting section on aggregates (thanks to whoever posted the link, was it Sita?), I learned a lot, but it still hasn't allayed my underlying concern that a program working with the data from the proposed mapping wouldn't be able to distinguish data about the "whole" from data about the "part", as noted in the discussion summary. Deborah Fritz showed a slide 14 at 33:36 that demonstrated an aggregated "chapter" relation very similar to the mapping Gordon supplied. Interestingly, Damian Iseminger's slide 10 at 1:04:30 has some similarity to my original mapping using the "aggregates" relation from expression to expression. Having that relation would make it clear which was which for the $t mapping, but then I wonder what other aspects of the whole description would need to change to make it fit the "aggegating" pattern. I have more to learn about aggregates!

In the case of the subfield r statements of responsibility, they can only be associated at the whole work manifestation level (whether the 505 is for a single volume work or perhaps 10 volumes...), right? That they'd be separated from the work or expression titles they should be connected to is to me also a concern, but not a huge one.

I'm going to vote not to include this additional mapping, which results in a loss, we could say due to the difficulty in mapping this scanty information in a way that identifies it appropriately as data about aggregated parts, and that could be dealt with differently when deciding whether to display or how to index the data. At least, let's make this a provisional decision, perhaps to be revisited when we get to the end and have encountered aggregates in other places which I'm sure we will (wait 'til we get to 773).

@CECSpecialistI
Copy link
Collaborator Author

I like the idea of mapping to a note on manifestation provisionally and revisiting when we tackle aggregates.

Associating statements of responsibility to the whole rather than the parts they should be connected to is a concern for me, but I don't know what we'd do as an alternative aside from throwing them into notes on the aggregated expressions which isn't great either. Right relationship or right entity? It's unfortunate we can't have both.

@GordonDunsire
Copy link
Collaborator

I assume that a mapping to note on manifestation will include most, if not all, of the tag/field contents, including titles and statements of responsibility for 'contents' that are embodied expressions.

In which case, I see little point in a separate mapping to rdamd: P30117 "has statement of responsibility". This element records only an unstructured description suitable for keyword indexing, as does rdamd:P30137 "has note on manifestation", and duplicate keywords are usually removed from the index ...

On the other hand, it is not a problem to record all of the statements of responsibility as rdamd:P30117 because RDA itself does not distinguish the source of information; there is no chief source of information and it is up to local communities to determine a priority order between, say, title page and contents page (just sayin') ...

I guess "formatted" applies only to syntax, not the semantics of 505 ;-)

@lake44me
Copy link
Collaborator

lake44me commented Jan 3, 2023

The description of $a kind of gives a hint for what "Formatted" connotes when it says "The text of the contents note may include titles, statements of responsibility, volume numbers and sequential designations, durations (for sound recordings), etc. For records formulated according to AACR rules, these elements are usually separated by ISBD punctuation." Whether there is an equivalent meaning under RDA would be a question, but for me the ISBD punctuation is the important formatting.

I think there are many libraries out there who want to present the gist of what's in the Table of Contents to the users of their discovery interface, and to do that, the association between contained titles and their creators or responsible parties (editors etc.), whether contained in statements of responsibility or identified as entities, needs to be maintained, as well as the order of contained works and the page numbers/additional information. So if we don't create "505" type notes for RDA cataloging, programmers will need to have enough data to assemble this for viewing or even linking/navigating to content for e-resources. However, this is more granularity of description that many libraries have taken on; perhaps this could be somewhat ameliorated by the cataloging interface making it simple to do, but there will have to be more complexity underneath.

@laura-ake
Copy link

It looks like @AdamSchiff gave several 505 examples that got inadvertently commented on the 561 issue. I'm not going to copy them here but will just link to the comment. Might come in useful when we get to testing or if we revisit this. I just posted a link to our catalog for my one example - hope the record stays there :-).

#225 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@lake44me lake44me

Labels
5XX MARC fields from the 5XX spreadsheet spreadsheet section assignment issues that reflect progress and provide general discussion space for sections of mapping work
Projects
MARC21 to RDA-RDF Mapping
Awaiting Review
Milestone
MVP for Transformation
Development

No branches or pull requests
7 participants
@lake44me @GordonDunsire @AdamSchiff @laura-ake @SitaKB @CECSpecialistI @pan-zhuo