https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39326
--- Comment #1 from Michaela Sieber <[email protected]> --- (In reply to Mathieu Saby from comment #0) > In ERM we can have an title, say /erm/eholdings/local/titles/8 which belong > to 2 packages. For each package I understand Koha will create a "resource" > (a rather vague term...) , say /erm/eholdings/local/resources/11 and > /erm/eholdings/local/titles/12 > > Currently the "title" contains bibliographical information (that will never > change : the title, publisher, isbn for a book, issn, etc), but also > information that depends on the package (the URL, the coverage dates for a > serial, a note about access, etc) > > I believe all those package-level information should be managed at the > "resource" level. Other ERM have something like "resource" and use it that > way. > > Clarifying this point could help resolve other difficulties like the > management of the kbart or the "biblio list" (some fields will be imported > as component of "title", other as components of "resource") > > What do you think of this proposal ? Generally I agree. But this would be a change of the existing data model because today a title record can exist without a resource record. Today the resource only exists if there is a link to at least one package. I think all attributes in title records match to the KBART format. These are: - publication_title - print_identifier - online_identifier - date_first_issue_online - num_first_vol_online - num_first_issue_online - date_last_issue_online - num_last_vol_online - num_last_issue_online - title_url - first_author - title_id - embargo_info - coverage_depth - notes - publisher_name - publication_type - date_monograph_published_print - date_monograph_published_online - monograph_volume - monograph_edition - first_editor - parent_publication_title_id - preceding_publication_title_id - access_type As far as I can see the upload of a KBART file (E-resource management>eHoldings> Local>Titles>Import from a KBART file) requires the choice of an existing package. In this case there will be resource records for all the uploaded titles from the KBART list. In my opinion it would be consistent to always create a resource record (even if you enter data manually) and keep the access data (like url, coverage, embargo,..) on the resource level. But as I said, this is not a small change. Maybe we should discuss that in Marseille ;-) -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
