Hi Tim, We find that the safest way of trimming frameworks to a more minimalist set is to "hide" the subfields. This can be quite laborious through the staff interface as you have to select each subfield and look in "Advanced constraints" then Visibility. If you have access at the sql level you can probably set the field "hidden" in table "marc_subfield_structure" to value -6 for those tags you do not want to appear (within your chosen framework). You might also want to change the tab for display to all be the same (eg "0") if you only have 18 tags. That just makes it clearer on the screen. Not every field has or needs to have a koha to marc mapping, but a few of the koha fields must be mapped to marc subfields. The Administration tool "MARC bibliographic framework test" and other tools in the same area should help fine tune it. We try to avoid removing fields (tags) and subfields from frameworks as you could lose bibliographic data if you switch between frameworks while editing and save the record. It depends what your longer-term plans might be for use of the system as to whether this might be a consideration. If you stray too far from the MARC standard tags you may find that searching for records becomes unreliable as the search indexes are fed from the fields and subfields according to the MARC21 (or UNIMARC) standard. Good luck. Ian On 28/05/2014 15:09, Alexander Tim wrote:
Not sure if this is the correct list to email but if not hoping someone can send me in the right direction!
So, I am not a Librarian but work as a sys admin for my company. We have a small Company Library that is used to publish various technical publications for our users to look through. We are looking to move to Koha but I find I am struggling with the initial steps of trimming down the MARC Framework. The list of fields I have been passed by our Librarian is for only 18 or so fields. I am therefore finding cutting down the default framework very laborious. I have looked to Import a cut down version of the framework, from an amended export to CSV, but this fails with "Error Importing the Framework". I was then hoping that there is something on the SQL side I could do to amend the framework but this has not exactly yielded any useful results. Is there anywhere I can check for an error on the framework import? If not is there any guidance on cutting a framework down to just the required fields?
I am also concerned that not every field we have in the proposed framework would have a corresponding Koha to MARC mapping. Would this be required or are these there for simplicity rather than a necessity?
Regards
Tim
Tindall Riley Marine (UK) Limited Authorised and regulated in the UK by the Financial Conduct Authority.
Registered Office: Regis House, 45 King William Street, London EC4R 9AN Company No: 8451968. V.A.T. No.: 174 7460 86 Tel: +44 (0)20 7407 3588 Fax: +44 (0)20 7403 3942
This email (and any attachments) is confidential and may be privileged. It may be read, copied and used only by the addressee. If you have received this in error, please contact us immediately.
_______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- Ian Bays Director of Projects, PTFS Europe Limited Content Management and Library Solutions +44 (0) 800 756 6803 (phone) +44 (0) 7774 995297 (mobile) +44 (0) 800 756 6384 (fax) skype: ian.bays email: ian.bays@ptfs-europe.com