Bug 39683 - suggestion.copyrightdate and suggestion.publicationyear
Summary: suggestion.copyrightdate and suggestion.publicationyear
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Database (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-04-18 20:03 UTC by Andrew Fuerste-Henry
Modified: 2025-04-18 20:11 UTC (History)
0 users

See Also:
GIT URL:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2025-04-18 20:03:44 UTC
The suggestions form in the user interface contains a field labeled "Copyright date." It gets saved in the database in suggestions.copyrightdate.

The database also contains the field suggestions.publicationyear. As far as I can tell, there is no way in the staff interface or OPAC to put a value in this field (though if one were to get a value into it, that value would show on /cgi-bin/koha/suggestion/suggestion.pl).

It would probably make sense to just remove suggestions.publicationyear from the database. But at the same time copyrightdate and publication date are really two distinct values ....

I'm mostly filing this bug for the next person to stumbles into this hole and wonders what that field's about. Hello, future person!
Comment 1 Katrin Fischer 2025-04-18 20:10:22 UTC
It's a bit more complicated. For historical reasons UNIMARC maps the publication year to publicationyear, while MARC21 has always been using copyrightdate. It's not easy to fix in existing databases where people can have changed the mappings, so we have a number of places in the code where we look at both dependent of the MARC flavor.
Comment 2 Katrin Fischer 2025-04-18 20:11:02 UTC
Hm, and now I realize we are talking about the suggestions table and not biblio/biblioitems... in that case maybe it can be fixed?