| Summary: | export list information in a MARC field of the record | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Mathieu Saby <mathsabypro> |
| Component: | Lists | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P5 - low | CC: | laurence.rault, m.de.rooy |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| GIT URL: | Initiative type: | --- | |
| Sponsorship status: | --- | Comma delimited list of Sponsors: | |
| Crowdfunding goal: | 0 | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
Mathieu Saby
2025-06-22 16:21:25 UTC
I don't know if there is any community interest in this, but it may be more complex to do than I thought. No standard MARC21 or UNIMARC field seems suitable, so for the development to be acceptable the field would probably need to be configurable for each installation in a syspref. So we can have for example in an given instance a repeatable 999 field, with the name of the list in a $a field, and its number in a $b field. It should concern only public list. 999$aOne list$b1 999$aAn other list$b2 Another approach would be to create a "virtual" field on the fly only when exporting to OAI-PMH. But adding or removing a record from a list would have to trigger an update of the record in the repository, and I don't know if that's possible. Note that the same idea could apply to course reserves. Laurence I add you as we talked about that during KohaLa Hackathon. |