From atge at kb.dk Tue Mar 15 13:02:59 2016 From: atge at kb.dk (Axel Teich Geertinger) Date: Tue, 15 Mar 2016 12:02:59 +0000 Subject: [mei-catalog-ig] MerMEId News Message-ID: <0B6F63F59F405E4C902DFE2C2329D0D1013FA037CD@EXCHANGE-03.kb.dk> Dear metadata and cataloging interest group We are happy to announce that a revised version of MerMEId is now available. Compared to versions available before last fall (that is, versions older than rev. 948), the most important changes include: * Upgrade to work with Tomcat 7.0.50+, Apache 2.2.*, Java 1.7.0_45+, and Orbeon 4.9. This has improved the file list's loading time and made possible a number of improvements. * A number of components have been moved to the eXist database to make them more easily customizable. This includes the XSL and CSS stylesheets used to generate the HTML preview; these are now located in /db/style/. It also includes lists such as the list of abbreviations, list of keywords and others, now located in /db/library/. * MerMEId's HTML preview now uses the Verovio toolkit to render incipits encoded in either MEI or Plaine and Easie code. Only the latter is editable directly in the MerMEId editor, however. The files at our demo server include a sample file called 'Incipit Demo' demonstrating this. * In the HTML preview, sources are no longer sorted automatically according to their classification. Sources are listed in the same order as in the XML file (and as in the editor, that is). * A script for generating multiple-file HTML output is now available (convenient for printing an entire catalogue, for instance). Its use is described in the updated manual. We have been using this feature for extracting the entire Carl Nielsen catalogue for further processing to a printed book (which is in print now and will appear very soon, by the way). * A new Rich Text Editor. MerMEId now uses the TinyMCE editor for text blocks instead of the YUI RTE. TinyMCE seems to be more reliable, and it is much easier to customize for use in MerMEId. The text editor's features now match the formatting options that MerMEId can actually handle. * A list of Frequently Asked Questions (FAQ) - mostly regarding the general use, installation, and customization of MerMEId - has been added to the manual. The FAQ is also on our web site: http://www.kb.dk/en/nb/dcm/projekter/mermeid/faq.html * A number of inputs etc. added, including references to authority files with person names and more details at source component and item level. To ensure best compatibility and fix potential flaws, the XSL transformation transform_mermeid_2_to_3.xsl found in the source code at /trunk/mermeid/transforms/mei/utils/ should be applied when migrating from older MerMEId versions (revisions 821-1042). As always, use at own risk - please make sure to back up your data before upgrading. The source code is available at GitHub: https://github.com/Det-Kongelige-Bibliotek/MerMEId You can try out MerMEId on our demo server: http://labs.kb.dk/editor/ Best wishes, Axel [http://support.kb.dk/images/kb_logo.jpg] Det Kongelige Bibliotek Nationalbibliotek og Københavns Universitetsbibliotek Axel Teich Geertinger Seniorforsker, centerleder | Senior Researcher, Head of Centre Det Kongelige Bibliotek | The Royal Library Dansk Center for Musikudgivelse | Danish Centre for Music Publication P.O. Box 2149 | DK-1016 København K tel +45 9132 4706 | Fax +45 3393 2218 | atge at kb.dk | www.kb.dk Besøgsadresse | Visiting address | Søren Kierkegaards Plads 1 Leveringsadresse | Delivery address | Christians Brygge 8 | 1219 København K EAN 5798 000 79 52 97 | Bank 0216 4069032583 | CVR 28 98 88 42 IBAN DK2002164069032583 | Swiftcode DABADKKK -------------- next part -------------- An HTML attachment was scrubbed... URL: -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.jpg Type: image/jpeg Size: 14433 bytes Desc: image001.jpg URL: From atge at kb.dk Wed Mar 16 10:21:40 2016 From: atge at kb.dk (Axel Teich Geertinger) Date: Wed, 16 Mar 2016 09:21:40 +0000 Subject: [mei-catalog-ig] Proposed changes to and in MEI 3.0.0 Message-ID: <0B6F63F59F405E4C902DFE2C2329D0D1013FA07F16@EXCHANGE-03.kb.dk> Hi Perry & metadata group Finally I have found some time to review the proposed changes to the header in the MEI 3.0.0 pre-release. I noticed a change in the model that I'd like to ask about. It has to do with the combination of structured and non-structured content. In our discussion in November (below) we were focusing on the grouping of events within event lists. This has been implemented in the new schema as agreed. No problem. In your original post you also addressed the content of the model (semi-structured vs. non-structured). I am sorry that I didn’t respond to that earlier. The current schema (2.1.0) has the following model for : whereas the proposed 3.0.0 schema has You and I had a private discussion about this in February/March 2013. Your conclusion then was: >I now think the best course of action is not to try to create two choices (semi-structured vs. free), >but rather to return to intermingling the elements of both options and letting the chips fall where they may. Then why did we end up having to choose between the two approaches now? If I have forgotten or overlooked something, please remind me. It causes me problems because personally, and because of the way MerMEId works, I prefer a rather structured approach. However, I still would like to be able to add an explanatory or descriptive text to the event also. The new