005 handling

MARC bib 005 >  Date and Time of Latest Transaction (NR)> Sixteen characters that indicate the date and time of the latest record transaction and serve as a version identifier for the record. They are recorded according to Representation of Dates and Times (ISO 8601). The date requires 8 numeric characters in the pattern yyyymmdd. The time requires 8 numeric characters in the pattern hhmmss.f, expressed in terms of the 24-hour (00-23) clock. https://www.loc.gov/marc/bibliographic/bd005.html

MARC Bib - Create Action

ScenariosFile / Actual outcome Expected outcome
No 005

NO005_vanityfair.mrc / Date and time the user loaded the bib record into FOLIO

same as actual 
Invalid 005

invalid005_vanityfair.mrc / Date and time the user loaded the bib record into FOLIO

same as actual 
Existing 005

vanity_fair_130.mrc / updates to the date and time the record was loaded into FOLIO

same as actual 

MARC Bib - Update Action 

ScenariosFile / Actual outcome Expected outcome
No 005

NO005_vanityfair_update.mrc / No 005.   > Will add 005 when user edits via quickMARC

005 is present and updated based on record when data import completes
Invalid 005

invalid005_vanityfair_update.mrc / Stores invalid value > Will 005 when user edits via quickMARC

Valid 005 is present and updated based on record when data import completes
Existing 005

existing005_drive_update.mrc / No change to date and time that was imported. 

Valid 005 is present and updated based on record when data import completes  MODSOURCE-642 - Getting issue details... STATUS

MARC Bib - Create - single record 

OCLC record ID / Actual outcomeExpected outcome 
1099843376 /  updates to the date and time the record was loaded into FOLIOsame as actual 

MARC Bib - Overlay - Single record

 OCLC record ID / Actual outcomeExpected outcome 
841319391 / 005 is updated same as actual 

MARC Bib - Create a new MARC bib - via quickMARC

Actual outcome Expected outcome 
Cannot test on snapshot Date and time the user created the bib record

MARC Bib - Derive a new MARC bib via quickMARC

Actual outcome Expected outcome 
Date and time the user derives the new bib record via quick MARCsame as actual 

MARC Bib - Update via quickMARC 

Actual outcomeExpected outcome 
Date and time the user edited the bib record via quickMARCsame as actual

MARC Bib > Linked authority update - via quickMARC

Actual outcomeExpected outcome
No change to 005 regardless of editing authority linked 1XX or deleting authority record 

MARC Bib > Linked authority update - via data import

Actual outcomeExpected outcome
No change to 005 regardless of editing authority linked 1XX

MARC auth 005 > Sixteen characters that specify the date and time of the latest record transaction and serve as a version identifier for the record. The data and time are recorded according to Representation of Dates and Times (ISO 8601) in the pattern yyyymmdd and hhmmss.f.


MARC Authority - Create Action

ScenariosFile / Actual outcome Expected outcome
No 005

No005_kesha_create.mrc / Date and time the user loaded the auth record into FOLIO

same as actual 
Invalid 005

invalid005_kesha_create.mrc / Date and time the user loaded the auth record into FOLIO

same as actual 
Existing 005

rosemary_prince.mrc / updates to the date and time the record was loaded into FOLIO

same as actual 

MARC Authority - Update Action 

ScenariosFile / Actual outcomeExpected outcome
No 005bad005_kesha_updates.mrc / No 005.   > Will add date and time when user edits via quickMARC005 is present and updated based on record when data import completes
Invalid 005

bad005_kesha_updates.mrc / Stores invalid value > Will update to valid date and time when user edits via quickMARC

Valid 005 is present and updated based on record when data import completes
Existing 005

updated_rosemary_prince.mrc / No change to date and time that was imported. 

Valid 005 is present and updated based on record when data import completes MODSOURCE-642 - Getting issue details... STATUS


MARC Auth - Update via quickMARC 

Actual outcomeExpected outcome 
Date and time the user edited the bib record via quickMARCSame as actual