https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34788
--- Comment #31 from Jonathan Field <[email protected]> --- (In reply to Mathieu Saby from comment #27) > Well, I am not your sponsor but as an average librarian I can say that it > not the most effective workflow : when we librarians download valid kbart > files from gokb or other sources, we usually wont want to edit the file to > remove columns that are not defined in kbart specs. If all mandatory fields > are in the file, won't it be possible to import the file with a "simple" > warning telling the user that the other (non mandatory) fields were > discarded? So, just so we understand this, is this because gokb actually don't follow the NISO standard, they add "proprietary" fields, is that correct? https://gokb.org/documentation/kbart-introduction.html#proprietary-gokb-fields. The majority of sample files we've been given or used are in NISO format and therefore load without problem. Are there other vendors who are also adding additional fields to the KBART NISO format? -- 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/
