| Summary: | MARC modification templates cannot check or change indicators | ||
|---|---|---|---|
| Product: | Koha | Reporter: | paxed <pasi.kallinen> |
| Component: | Tools | Assignee: | Bugs List <koha-bugs> |
| Status: | NEW --- | QA Contact: | Testopia <testopia> |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | a.roussos, abales, aholt, alban.peyrat_koha, andrew, aspencatteam, barbara.johnson, bibliwho, black23, bugzilla, chanel.wheeler, Chip.Halvorsen, ctodd, david, dcook, enica, flyingendpaper, george, hayleypelham, helm.consortium, horganl, jrobb, jvinke, kati.sillgren, kelly, koha, lauren_denny, marjorie.barry-vila, martin.renvoize, mathsabypro, mchen, mnero, mspinney, phil |
| Version: | Main | ||
| Hardware: | All | ||
| OS: | All | ||
| Change sponsored?: | --- | Patch complexity: | --- |
| Documentation contact: | Documentation submission: | ||
| Text to go in the release notes: | Version(s) released in: | ||
| Circulation function: | |||
|
Description
paxed
2018-11-19 11:24:05 UTC
As an enhancement to Koha's Marc Modification Template, it would be extremely helpful to include indicators as part of this process. A lot of libraries would like an easy way to remove their 7 indicators in 650 tags. +1, would love to see this This would be such a great time saver. Currently we have to create a report to capture the correct bibs, export them, update and import them back in. It would be great to be able to do it in Koha instead. +1 This is an oversight I'd like to see change. Indicators are a part of the MARC field afterall. +1 This would be SO helpful!! There hasn't yet been one instance that I've been able to try using the MARC modification templates because every way they'd be helpful for us involves essential information from the indicators, changes to the indicators, etc. Are you working on this one Hayley? Would be lovely to see some code. Hi Martin, I am in the process of trying to get client sign off on some work that'd been done in this area. Anyone feel free to pick it up in the meantime if you have some time! Cheers, Hayley If the field we are adding has indicators that are significant, this would enable user to do this action in Koha. Without it, I would need to use MarcEdit to change the indicators, so I might as well use it to add the field at the same time. If we can do this in Koha rather than outside of Koha, it would vastly streamline the process and allow users without MarcEdit experience to change bibs by simply selecting the correct Marc Modification Template. Another alternative would be if one could add a run a macro as an action in the marc modification template, since we can change indicators using a macro. There are several type of subject headings that we would like to automatically exclude when importing a record from OCLC for instance. We have no need for the 650 5 Canadian 650 6 Répertoire de vedettes-matière, etc. In the 650 7 if we could limit only certain +2 that would be good as well sears and bisacsh headings. Just one man's opinion Exactly, Laura! We would love to be able to do that, but can't with the templates unable to act based on indicator data. Is this a particularly difficult enhancement? It would be super helpful. Bug initially created in 2018. Does it need to be a paid-for development? (In reply to AspenCat Team from comment #13) > Is this a particularly difficult enhancement? It would be super helpful. Bug > initially created in 2018. Does it need to be a paid-for development? It wouldn't be that hard... except the simplest change would not be accepted, as all new stuff must use Koha Objects. So, you'd have to convert C4/MarcModificationTemplates.pm to Koha/MarcModificationTemplate.pm, Koha/MarcModificationTemplates.pm, Koha/MarcModificationTemplateAction.pm, Koha/MarcModificationTemplateActions.pm (or something along those lines), change all the scripts that use the marc modification templates to use those new objects, rewrite tests, ... Too much of a hassle. Offers of sponsorship always help a bug move forward, else a developer is either trying to justify time working on a bug to their boss for no obvious financial reward or working on the bug in their spare time. As for paxed comment regarding difficulty and C4 vs Koha.. I would say this is an area where you could happily continue in C4 space. It's not a hard requirement to rewrite the whole of Koha to refine an existing feature.. QA would push for Unit tests however, even for a C4 change.. but that's just standard good practice. Hi It would be useful for unimarc users too. I see the bug is assigned. Is someone working on it ? (In reply to Mathieu Saby from comment #16) > Hi > It would be useful for unimarc users too. > I see the bug is assigned. Is someone working on it ? I don't think it is being worked on at the moment. I have changed to unassigned. +1 This would be very useful. +1 - This would be a big help. |