Bug 36552 - Update record 'date entered on file' when duplicating a record
Summary: Update record 'date entered on file' when duplicating a record
Status: Pushed to oldstable
Alias: None
Product: Koha
Classification: Unclassified
Component: Cataloging (show other bugs)
Version: Main
Hardware: All All
: P3 minor (vote)
Assignee: Janusz Kaczmarek
QA Contact: Marcel de Rooy
URL:
Keywords:
Depends on:
Blocks: 36792
  Show dependency treegraph
 
Reported: 2024-04-09 12:41 UTC by Janusz Kaczmarek
Modified: 2024-05-28 22:48 UTC (History)
4 users (show)

See Also:
Change sponsored?: ---
Patch complexity: Small patch
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
24.05.00,23.11.06,23.05.12


Attachments
Bug 36552: Update record 'date entered on file' when duplicating a record (3.00 KB, patch)
2024-04-09 12:52 UTC, Janusz Kaczmarek
Details | Diff | Splinter Review
Bug 36552: Update record 'date entered on file' when duplicating a record (3.06 KB, patch)
2024-04-11 13:17 UTC, Victor Grousset/tuxayo
Details | Diff | Splinter Review
Bug 36552: Update record 'date entered on file' when duplicating a record (3.16 KB, patch)
2024-04-12 08:12 UTC, Marcel de Rooy
Details | Diff | Splinter Review
Bug 36552: (QA follow-up) Add POSIX module (1.23 KB, patch)
2024-04-12 08:12 UTC, Marcel de Rooy
Details | Diff | Splinter Review
Bug 36552: (QA follow-up) Add a theoretical check on $record (1.56 KB, patch)
2024-04-12 08:12 UTC, Marcel de Rooy
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Janusz Kaczmarek 2024-04-09 12:41:44 UTC
The 'date entered on file' (MARC21: 008/0-5, UNIMARC: 100a/0=7) of a record created by duplication of an existing record should be set to the current date instead of having the value of the original record.
Comment 1 Janusz Kaczmarek 2024-04-09 12:52:06 UTC
Created attachment 164556 [details] [review]
Bug 36552: Update record 'date entered on file' when duplicating a record

The 'date entered on file' (MARC21: 008/0-5, UNIMARC: 100a/0=7) of a record created
by duplication of an existing record should be set to the current date instead of
having the value of the original record.

Test plan
=========
1. Check the 'date entered on file' of an existing biblio / authotiry record
   (MARC21: 008/0-5, UNIMARC: 100a/0=7).
2. Duplicate the record by Edit > Edit as new (duplicate)
3. Control the 'date entered on file' value - it will equal to that of the
   original record.
4. Apply the patch (restart plack).
5. Repeat step 2.
6. Check the date - it should be the current date.
Comment 2 Victor Grousset/tuxayo 2024-04-11 13:17:07 UTC
Created attachment 164687 [details] [review]
Bug 36552: Update record 'date entered on file' when duplicating a record

The 'date entered on file' (MARC21: 008/0-5, UNIMARC: 100a/0=7) of a record created
by duplication of an existing record should be set to the current date instead of
having the value of the original record.

Test plan
=========
1. Check the 'date entered on file' of an existing biblio / authotiry record
   (MARC21: 008/0-5, UNIMARC: 100a/0=7).
2. Duplicate the record by Edit > Edit as new (duplicate)
3. Control the 'date entered on file' value - it will equal to that of the
   original record.
4. Apply the patch (restart plack).
5. Repeat step 2.
6. Check the date - it should be the current date.

Signed-off-by: Victor Grousset/tuxayo <victor@tuxayo.net>
Comment 3 Victor Grousset/tuxayo 2024-04-11 13:17:40 UTC
It works! :)

tested marc21 and unimarc
Comment 4 Victor Grousset/tuxayo 2024-04-11 14:18:52 UTC
(with biblios and authorities)
Comment 5 Marcel de Rooy 2024-04-12 07:07:19 UTC
(In reply to Janusz Kaczmarek from comment #0)
> The 'date entered on file' (MARC21: 008/0-5, UNIMARC: 100a/0=7) of a record
> created by duplication of an existing record should be set to the current
> date instead of having the value of the original record.

Hi Janusz,
Do you have any supporting information for this statement?
Comment 6 Janusz Kaczmarek 2024-04-12 07:38:30 UTC
(In reply to Marcel de Rooy from comment #5)
> (In reply to Janusz Kaczmarek from comment #0)
> > The 'date entered on file' (MARC21: 008/0-5, UNIMARC: 100a/0=7) of a record
> > created by duplication of an existing record should be set to the current
> > date instead of having the value of the original record.
> 
> Hi Janusz,
> Do you have any supporting information for this statement?

Hi Marcel,

Thank you for having a look at this.

I would say, this is just the cataloguers knowledge, common sense, and interpretation of the term "date entered on file".

From https://loc.gov/marc/bibliographic/bd008a.html:

>>>>>

00-05 - Date entered on file

Computer-generated, six-character numeric string that indicates the date the MARC record was created. Recorded in the pattern yymmdd.

Pattern yymmdd is yy for the year, mm for the month, and dd for the day. The date entered on file in 008/00-05 is never changed. The date and time of latest transaction information in field 005 changes each time a transaction is made to the record. The latest transaction information enables an organization handling more than one version of a record to identify the most current version. The fill character (|) is not allowed in any of these positions. Field 008/00-05 is usually system generated.

<<<<<

The logic is: If you are creating a record in Koha with the function "Edit as new (duplicate)" it means, in fact, that you are creating a completely new record, with no connection to the original one, except that you want to use it as a template.  Hence it should have the current date in 008/0-5 (and respectively 100 $a/0-7 in UNIMARC). 

Cataloguers I work with have asked for this since always and I put in in my installations, now sharing this with the community. 

NB the phrase "The date entered on file in 008/00-05 is never changed" from MARC 21 definition above should be, obviously, interpreted in respect to a specific record and not to all records that somebody has created being inspired by this record.  This would have no sense, IMVHO.
Comment 7 Marcel de Rooy 2024-04-12 08:00:14 UTC
(In reply to Janusz Kaczmarek from comment #6)
> I would say, this is just the cataloguers knowledge, common sense, and
> interpretation of the term "date entered on file".

Yes, sounds okay to me. Couldnt find a more authorative answer myself than the LOC page you cited.
Comment 8 Marcel de Rooy 2024-04-12 08:12:41 UTC
Created attachment 164800 [details] [review]
Bug 36552: Update record 'date entered on file' when duplicating a record

The 'date entered on file' (MARC21: 008/0-5, UNIMARC: 100a/0=7) of a record created
by duplication of an existing record should be set to the current date instead of
having the value of the original record.

Test plan
=========
1. Check the 'date entered on file' of an existing biblio / authotiry record
   (MARC21: 008/0-5, UNIMARC: 100a/0=7).
2. Duplicate the record by Edit > Edit as new (duplicate)
3. Control the 'date entered on file' value - it will equal to that of the
   original record.
4. Apply the patch (restart plack).
5. Repeat step 2.
6. Check the date - it should be the current date.

Signed-off-by: Victor Grousset/tuxayo <victor@tuxayo.net>

Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Comment 9 Marcel de Rooy 2024-04-12 08:12:44 UTC
Created attachment 164801 [details] [review]
Bug 36552: (QA follow-up) Add POSIX module

Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Comment 10 Marcel de Rooy 2024-04-12 08:12:46 UTC
Created attachment 164802 [details] [review]
Bug 36552: (QA follow-up) Add a theoretical check on $record

Theoretically, it might be empty? Note the check too in the
other script.

Signed-off-by: Marcel de Rooy <m.de.rooy@rijksmuseum.nl>
Comment 11 Katrin Fischer 2024-04-12 12:06:25 UTC
Pushed for 24.05!

Well done everyone, thank you!
Comment 12 Fridolin Somers 2024-05-23 12:57:32 UTC
Pushed to 23.11.x for 23.11.06
Comment 13 Lucas Gass 2024-05-28 19:26:45 UTC
Backported to 23.05.x for upcoming 23.05.12