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

dmd/flatten: Support more than MARC 533$a #68

Closed
RussellMcOrmond opened this issue Jan 11, 2023 · 5 comments
Closed

dmd/flatten: Support more than MARC 533$a #68

RussellMcOrmond opened this issue Jan 11, 2023 · 5 comments

Comments

@RussellMcOrmond
Copy link
Contributor

RussellMcOrmond commented Jan 11, 2023

This is: 533 - Reproduction Note
https://www.loc.gov/marc/bibliographic/bd533.html

foreach my $source ( $record->field('533') ) {
my $ss = normaliseSpace( $source->subfield('a') );
if ( length($ss) ) {
addArray( \%flat, 'no_source', $ss );
}
}

@RussellMcOrmond
Copy link
Contributor Author

Example @nataliemacdonald gave for https://www.canadiana.ca/view/oocihm.8_00559 , indicating that the no_source field should read "Electronic resource: Ottawa : Canadiana.ca, 2017."

  <datafield tag="533" ind1=" " ind2=" ">
    <subfield code="a">Electronic resource:</subfield>
    <subfield code="b">Ottawa :</subfield>
    <subfield code="c">Canadiana.org,</subfield>
    <subfield code="d">2017.</subfield>
  </datafield>

@RussellMcOrmond
Copy link
Contributor Author

RussellMcOrmond commented Jan 11, 2023

Questions for @nataliemacdonald ,

  • Do we need to scan existing MARC records to look for examples where $b, $c, or $d are used to ensure that we aren't exposing anything that wasn't recorded correctly, or can be assume all MARC records currently stored would meet the new criteria?

  • Are there other 533 subfields that should be supported, and can you offer suggestions of how they should be displayed as well as MARC sample files?

@RussellMcOrmond RussellMcOrmond changed the title dmd/flatten: Support more than 533$a dmd/flatten: Support more than MARC 533$a Jan 11, 2023
@RussellMcOrmond
Copy link
Contributor Author

Full record as XML (Use MarcEdit to convert back to a MARC binary file for testing with uploader).

oocihm.8_00559-MARC.xml.txt

@RussellMcOrmond RussellMcOrmond self-assigned this Jan 23, 2023
@RussellMcOrmond
Copy link
Contributor Author

RussellMcOrmond commented Jan 23, 2023

I'm authoring a tool to scan all existing MARC records for there being more than a subfield 'a', and then output the concatenated record as a file for someone in Heritage Services to scan.

It isn't only "new" records that have to work with any change to the MAP, but all existing records.

https://metacpan.org/pod/MARC::Field#as_string(-[$subfields]-[,-$delimiter]-)

By default all subfields will be used in the XML order with a space between them. We may want to do something different, and only include a subset of subfields in the record.

Possibly only 'abcd' or 'abcdef'?

@RussellMcOrmond
Copy link
Contributor Author

The tool skips any that only have an "a" subfield, and thus would be the same before and after any MAP change.

russell@eclipse:/media/crkn-nas-wip$ wc -l  _Metadata_Synchronised/analysis/MARC533lists/*
       2 _Metadata_Synchronised/analysis/MARC533lists/access-ams-MARC533.csv
       6 _Metadata_Synchronised/analysis/MARC533lists/access-omcn-MARC533.csv
   89035 _Metadata_Synchronised/analysis/MARC533lists/access-oocihm-MARC533.csv
      95 _Metadata_Synchronised/analysis/MARC533lists/access-oocihm.N-MARC533.csv
      12 _Metadata_Synchronised/analysis/MARC533lists/access-ooe-MARC533.csv
       5 _Metadata_Synchronised/analysis/MARC533lists/access-oop-MARC533.csv
       2 _Metadata_Synchronised/analysis/MARC533lists/access-qmma-MARC533.csv
   89157 total
russell@eclipse:/media/crkn-nas-wip$ 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants