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.

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

008 Fixed-length data elements general information #50

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

008 Fixed-length data elements general information #50

CECSpecialistI opened this issue Nov 25, 2021 · 63 comments
Labels
00X MARC fields from the 00X spreadsheet coded-rip field in category "review in progress" with coding complete for this level; to be reviewed later spreadsheet section assignment issues that reflect progress and provide general discussion space for sections of mapping work
Milestone

Comments

@CECSpecialistI
Copy link
Collaborator

https://github.com/uwlib-cams/MARC2RDA/blob/main/Working%20Documents/00X.csv

@CECSpecialistI CECSpecialistI added spreadsheet section assignment issues that reflect progress and provide general discussion space for sections of mapping work 00X MARC fields from the 00X spreadsheet labels Nov 25, 2021
@CECSpecialistI CECSpecialistI added this to the PCC RDA BSR milestone Nov 30, 2021
@SitaKB SitaKB self-assigned this Apr 1, 2022
@SitaKB
Copy link
Collaborator

SitaKB commented Apr 12, 2022

TAG 008 has [OBSOLETE] characterPositionLabels. What to do with? Should it be mapped or ignored? @CECSpecialistI @AdamSchiff

@SitaKB
Copy link
Collaborator

SitaKB commented Apr 19, 2022

Certain MARC TAGS can be mapped to more than one RDA properties. How should we record this in the mapping?

@CECSpecialistI
Copy link
Collaborator Author

It depends on the MARC TAG and properties in question, I think. Some may merit two or more mappings, and in that case, they can go on separate spreadsheet rows. Otherwise, we need to choose the best property and map to that one. Does that answer your question @SitaKB , or were you getting at something else? Sorry I missed this until now, we could have talked about it at the meeting.

@SitaKB
Copy link
Collaborator

SitaKB commented Apr 27, 2022

I noticed that sometimes the character position number is missing or wrong. For example 008- Biography has character positon empty and 39. According to https://www.loc.gov/marc/bibliographic/bd008b.html it should be 34. @CECSpecialistI
@AdamSchiff

@CECSpecialistI
Copy link
Collaborator Author

Uh oh! Do you think this is a spreadsheet problem or an error in the data?

@SitaKB
Copy link
Collaborator

SitaKB commented Apr 27, 2022

Don't know. 007 file alsohad unknown character position like 4435 but the new file has the right number. All the 44XX are now gone from 007.
Old upload
44355 Image bit depth 001-999 Exact bit depth 007 00 c
Recent file
06-08 Image bit depth 001-999 Exact bit depth 007 00 c

@cspayne
Copy link
Collaborator

cspayne commented Oct 3, 2024

@CECSpecialistI Form of Item "r" is a valid code describing the reproduction for records that meet the reproduction conditions (presence of 533) for Photocopy/Print on Demand reproductions https://www.loc.gov/aba/rda/mgd/mg-reproductionsPhotocopies.pdf . We are not getting specific about the content of the 533 here (let's see whether we need to when we get some output)) but it specifies that $a contains only "Print reproduction".

If a record meets one of the Reproduction Conditions but "Form of Item" contains a code that isn't specified in the PCC instructions (all of which are clearly intended to describe the reproduction rather than the original), then we are taking the approach that these are cloning mistakes, and therefore must apply to the original. "x" and "z" fall into that category. The transformation logic makes use of this generally (i.e. doesn't apply specifically to the code on that line). Note != means not equal to.

"If a Reproduction condition is present, AND if value != a, b, c, o, or r, apply mapping and transformation to OriginalM, not ReproM. - LA, DC 2024-09-12"

Does this make sense?

Yes this makes sense! Thank you.

cspayne added a commit that referenced this issue Oct 3, 2024
@cspayne cspayne added code on hold Decisions or answers to questions needed before coding can continue and removed code on hold Decisions or answers to questions needed before coding can continue labels Oct 8, 2024
@cspayne
Copy link
Collaborator

cspayne commented Oct 28, 2024

Hi @SitaKB Thank you for your answers to all of my questions.

I am still unclear on which dates I should code and which are only applicable to aggregates. Are 008/06 = i or k (inclusive dates of collection and range of years of bulk of collection) only for aggregate works?

cspayne added a commit that referenced this issue Oct 28, 2024
@cspayne
Copy link
Collaborator

cspayne commented Oct 28, 2024

"The mappings on lines 924 (MUSIC) and 753 (MIXED MATERIALS) are the only 2 Form of Item “i” codes for Multimedia [OBSOLETE] that map to expression property https://rdaregistry.info/Elements/e/#P20001 "has content type”. Line 753 (MIXED MATERIALS) also maps Form of item “i” to http://rdaregistry.info/Elements/m/P30002 "has media type”. Line 428 (CONTINUING RESOURCES) and Line 184 (BOOKS) map Form of Item “i” to http://rdaregistry.info/Elements/m/P30001 "has carrier type.” Should they all map to manifestation for consistency?"

@SitaKB I think this is the only other outstanding question

@cspayne I think for music and mixed materials EXPRESSION was chosen for a reason.

@tmqdeborah
Copy link
Collaborator

tmqdeborah commented Oct 28, 2024

Hi @SitaKB Thank you for your answers to all of my questions.

I am still unclear on which dates I should code and which are only applicable to aggregates. Are 008/06 = i or k (inclusive dates of collection and range of years of bulk of collection) only for aggregate works?
@cspayne
The 008/06 = i or k (inclusive dates of collection and range of years of bulk of collection) are only appropriate for Collection works (not Collection aggregate manifestations). Collection works (and Diachronic works) are also being 'pulled' for Phase I (in addition to Collection aggregates). So, these transforming these codes could wait until Phase II (unless transformation instructions are already available and correct) in which case you could just go ahead and do them.

@sarahruska sarahruska modified the milestones: MVP for Transformation, PCC RDA BSR Oct 29, 2024
@cspayne
Copy link
Collaborator

cspayne commented Oct 31, 2024

Hi @SitaKB, I am still confused about the dates 1 and 2 mappings. It appears that the mappings account for a value in date 1 or a value in date 2 or when both are blank, but I am not seeing a row for when there is a value in date 1 and date 2.
Hi @cspayne You mean for multiple dates (m), value for date 1 and date 2 are missing. We forgot to add it then.
I am also unclear on what the transformation notes mean, such as "[date1..date2] | u=blank | partial blank = fill in blanks as X" and "[date]/.. | u=blank"
It is not clear to me what the date value should look like in RDA. Are you able to go through and clarify the mappings and transformation notes for these dates?
Hi @cspayne This note for (q) questionable date means I think if blank then the value u (f.e.19uu) | when it is partial blank then the value X (f.e. 1920-19XX). I am also not sure.

@cspayne
Copy link
Collaborator

cspayne commented Nov 3, 2024

Hi @CECSpecialistI, @GordonDunsire , and @szapoun
I took a look at meeting notes and found some about the 008 dates from November 23, 2022. Do you happen to remember why 008/06 = 'm' does not have a mapping for when both date1 and date2 are present?

cspayne added a commit that referenced this issue Nov 3, 2024
cspayne added a commit that referenced this issue Nov 4, 2024
@GordonDunsire
Copy link
Collaborator

@cspayne: I don't recall the discussion. I note that the code 'm' means two different things: dates of a diachronic manifestation, and date range of manufacture of a produced manifestation (artisanal, etc.). We are excluding diachronic manifestations, etc. from phase 1, so only the date range of manufacture is of interest, but that only makes sense if both dates have values; that is, if it is a valid date-based timespan. If either date is 'missing', the value is not a valid timespan; instead, it is an 'encyclopedic' statement: we know this took more than a year to paint before it first appeared in an exhibition, but we don't know how long.

If there is a separate condition for determining if the manifestation is produced (rather than published), then I think it is ok to output a concatenation of dates as 'date of production', but it is not ok when either date is blank or blanked.

@CECSpecialistI
Copy link
Collaborator Author

@SitaKB volunteered to add this mapping during meeting 2024-11-13

@SitaKB
Copy link
Collaborator

SitaKB commented Nov 13, 2024

@cspayne I have added 008/06 =m to the mapping when both date1 and date2 are present.

@lake44me
Copy link
Collaborator

lake44me commented Nov 14, 2024

@SitaKB @cspayne If it's the line I think it is (currently 31), should the uncategorized note "edtf for time interval with unknown start " be changed to something else (maybe just "edtf for time interval")?
Minor niggling point - I was just checking that the reproduction condition was there (thank you Sita).

@SitaKB
Copy link
Collaborator

SitaKB commented Nov 14, 2024

@lake44me You are right Laura. I didn't read the sentence properly. I have correted it. Thanks

cspayne added a commit that referenced this issue Nov 21, 2024
cspayne added a commit that referenced this issue Nov 21, 2024
@cspayne cspayne added coded-rip field in category "review in progress" with coding complete for this level; to be reviewed later and removed coding-rip field in category "review in progress" with transformation coding in progress code on hold Decisions or answers to questions needed before coding can continue meeting discussion needed asynchronous discussion needed labels Nov 21, 2024
cspayne added a commit that referenced this issue Jan 6, 2025
cspayne added a commit that referenced this issue Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
00X MARC fields from the 00X spreadsheet coded-rip field in category "review in progress" with coding complete for this level; to be reviewed later spreadsheet section assignment issues that reflect progress and provide general discussion space for sections of mapping work
Projects
Status: Review in Progress
Development

No branches or pull requests