[MCN-L] Posting to new groups.io list
Hi, I tried posting to the new address from Thunderbird, but nothing appeared. There are apparently no messages at all, despite it having been 'up' for a month: As a follow-up I tried submitting a message via their web interface, and got this message: It will be interesting to see whether, and when, this approval happens. At present, the new home for the MCN list has all the hallmarks of a non-operative setup. Richard -- *Richard Light* richardlight...@gmail.com /@richardofsussex/ ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://lists.mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
Re: [MCN-L] LAM interoperability SIG
On 2016-02-23 10:18 PM, Stefano Cossu wrote: Hi there, 1. At the moment we are not exchanging data with other institutions in a "smart" way. The recent work on our new DAMS will bring more opportunity in this direction though. The key for this is having adopted RDF as the lingua franca for our DAMS. Before we tackle inter-institutional interoperability, we want to better connect departments within the museum and heterogeneous data sets such as library, archives and collections. This will have more obvious and immediate advantages for us. Harmonizing library, museum and archive catalogue data into RDF (if that's what you mean) would be a significant achievement. Clearly, it would be of much wider value than within your own institution. Certainly it's an aspiration which this group should support you in/help you with. 2. CIDOC CRM seems to be the most comprehensive and flexible ontology to encompass the widest range possible of cultural heritage items. However, CIDOC CRM cannot be practically used as a cataloging ontology, but rather as a harmonization tool. It should sit between the cataloger and the consumer, and accessed only to machines that can handle its full complexity. The approach I have adopted is to generate Linked Data RDF on the fly, starting in my case from native museum catalogue data encoded in XML records [1]. The idea is that each object in the [Wordsworth Trust] collection is published with its own unique, persistent, useful URL. I would commend this strategy as a good way to get started: stake a claim for your collection in the Web information space. I'm working to improve the RDF, and one way of doing that would be to include more CIDOC-CRM structure in it. The other, bigger, problem I see is that all the data is just string values. What we desperately need are more shared Linked Data frameworks (for people, places, events, ...), whose URLs we can begin to embody in our catalogue data. If you see 'interchange' as a selective publication exercise, rather than a mass-data-shifting one, then there is no down-side to just publishing that subset of your catalogue data which is useful for sharing. Museum records are full of internal management stuff which has no place being published, just as bibliographic records contain lots of technical MARC data that won't be of interest to a general public. One useful thing we can do is to agree what story we are trying to tell, and work back from that conclusion to a view on what data is required for sharing. (Also, dynamically rendering catalogue data on request ensures that it is always up to date.) There are several publishing schemata that map to CIDOC-CRM and expose only the concepts meaningful to a human end user. There is not, as far as I know, a cataloging schema that is encoded in RDF and maps to CIDOC CRM. I am aware of ongoing efforts to serialize the Getty's AAT (which contains CDWA terms) into RDF [1], but having a separate, formalized cataloging ontology based on CDWA would be a great advancement in this area. Note that all three Getty 'vocabularies' (should one now say 'ontologies'?) are fully published as Linked Data, and so are available as RDF. Best wishes, Richard Light [1] e.g. http://collections.wordsworth.org.uk/Object/WTcoll/id/GRMDC.C144.9 which resolves to http://collections.wordsworth.org.uk/Object/WTcoll/id/rdf/GRMDC.C144.9 when RDF is requested 3. We use Fedora [2] which is completely content-agnostic and allows to build any sort of content model. Fedora and its satellite projects encourage the use of PCDM [3] as a very basic and broad-scoped ontology on top of which more domain-specific ontologies can be layered to satisfy any kind of content modeling. 4. My team (5 people) is in charge of designing and implementing our collection information systems. A separate department, Digital Experience and Access, acts as a broker for end users' (staff and public) needs and is in constant dialog with us. I act as an interpreter who translates semi-technical requirements into specifications. [1] http://www.getty.edu/research/tools/vocabularies/lod/index.html [2] http://fedorarepository.org [3] https://github.com/duraspace/pcdm/wiki On Thu, 18 Feb 2016 16:33:51 + "Delmas-Glass, Emmanuelle" <emmanuelle.delmas-gl...@yale.edu> wrote: Dear all, In order to get us started with the LAM interoperability SIG, we would like to get your feedback on a few questions. 1. Use cases: as a museum, library or archive, whenever you tried to integrate your data with other institutions, what worked, what didn't, and why? 2. Interoperable metadata schemas and/or ontologies: what is out there that can help bring collection data and bibliographical data together? What do you think about them, what are the challenges and how do you plan or wish to utilize them? 3. Existing interoperability tools: what software platforms do you use? If you could design your o
Re: [MCN-L] Walters Art Museum goes CC0
Hi, While that's great news, AFAICT the data is still only accessible via a [custom] API, for which a key is required. Are there plans for bulk downloads and/or Linked Data support? Richard On 30/07/2015 16:47, Sarah Stierch wrote: In an unprecedented move. In 2012 the Walters Art Museum went CC BY SA 3.0 for their image licensing. Today, they go CC0 - releasing both images and metadata under the most free of Creative Commons licenses, making a public domain declaration. http://openglam.org/2015/07/30/walter-art-museum-goes-cc0/ Sarah Stierch - Museumist specializing in open culture and grantwriting www.sarahstierch.com http://www.sarahstierch.com/ ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/ -- *Richard Light* ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
Re: [MCN-L] Links in TMS notes field
A technique I have found useful when pasting content from Word (into a standard web page) is to use a simple text editor such as Notepad as an intermediary. Copy the text in Word, paste it into Notepad, re-select and re-copy it, then paste into the target field/form. If you want to retain simple HTML markup, while losing the horrors of Word style information, it may be that a rich text editor could usefully take the place of Notepad as the intermediary. Advice, anyone? Richard On 07/01/2015 14:41, Ben Rubinstein wrote: Veering slightly off topic, but if you do anything en-masse based on the TextEntryHTML field of the TextEntries, be prepared for some hidden horrors - if users paste text in directly from Word or similar programmes, you can get some really unpleasant mark-up in there. In many applications you won't want to dump it directly to a web page. Ben On 07/01/2015 14:25, Smith, Jeffrey wrote: John, We have simply dropped in the required href text and used the web page to render it correctly. The text entry functionality is not an HTML editor (though that would be nice), but you can copy the text from an HTML source, paste it into a text entry field, and TMS will save a version in the table's TextEntryHTML field. I'veattached a sample row from our database. -Original Message- From: mcn-l-boun...@mcn.edu [mailto:mcn-l-boun...@mcn.edu] On Behalf Of Gordy, John Sent: Wednesday, January 07, 2015 9:13 AM To: mcn-l@mcn.edu Subject: [MCN-L] Links in TMS notes field Calling on the MCN Collective Hive Mind At an individual object level in TMS there is a Notes tab and within Notes there are Text Entries Text Entries are a rich text field and any bracketed text is rendered to the page. Does anyone know how to create hyperlinks within the Text Entries? I know it can be done. We even have examples of links within our own entries but they were created prior to the RTF formatting Thanks in advance John Gordy Chief of Digital Outreach National Gallery of Art ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/ -- *Richard Light* ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l@mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://www.mail-archive.com/mcn-l@mcn.edu/
[MCN-L] FW: Soliciting Terms for Nomenclature 4.0
Hi, I'm delighted to hear that Nomenclature is still thriving and developing. Am I right in thinking that it is still entirely a dead trees publication, with no online manifestation at all? Might this be the time to take a big leap forward, and publish Nomenclature 4.0 as Linked Open Data, maybe as a SKOS ontology? Where the Getty lead, and all that ... Richard On 15/05/2014 14:12, John T. Hart wrote: Please excuse any cross-postings. Fellow Museum Professional(s): Since its inception in 1978 many of us have come to use Chenall's Nomenclature to categorize and organize our museum collections. Now in its third edition, the Nomenclature Task Force of AASLH is preparing to undertake a project to release Nomenclature 4.0, but we can't do it without your input and help! We are asking you, as the frontline of museum collections, to recommend new terms, alternative categories for objects, and new definitions of objects. It's easy to do and won't take but a few minutes and can all be done online. If you go to this link: (http://community.aaslh.org/nomenclature-submissions/) you can choose the best option for what you'd like to submit and add information to the form, provide us with your contact information in case we have any questions or need to follow up with you, hit submit and you're all done. It's that easy! We are open to any suggestions you have and rest assured we give thought to each and every recommendation sent in to us. If you have any questions, please feel free to contact me directly and I will try to answer your question(s) myself or share them with the Task Force to address them. Thank you for your help and your time! John John Hart, Jr. Museum Registrar and AASLH Nomenclature Task Force Member Sullivan Museum and History Center Norwich University 158 Harmon Drive Northfield, VT 05663 (802) 485-3289 ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l at mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://mcn.edu/pipermail/mcn-l/ -- *Richard Light*
[MCN-L] LODLAM Patterns - Call for Participation
This initiative chimes with work being undertaken by the CIDOC Documentation Standards Working Group. We have made a start at defining some specific issues to address [1], though not much progress has subsequently been made on actually addressing them. Richard Light [1] http://network.icom.museum/cidoc/working-groups/documentation-standards/docstandards-lddp/ On 07/08/2013 20:06, Richard Urban wrote: We invite you to join a collaborative effort to identify design patterns for Linked Data in Libraries, Archives, and Museums (LODLAM). A LODLAM design pattern identifies common problems, solutions, and examples found in current LAM metadata standards and emerging Linked Data approaches. Participants are invited to use the LODLAM Proto-Patterns wiki (http://lodlampatterns.org/protopattern) as platform for identifying potential problems, solutions, and contexts. In the wiki these patterns can be edited, refined, classified, and further developed over time. The results of this study will be used to understand what patterns exist in our current environment and what patterns are desirable as we move towards Linked Data approaches. In other disciplines, design patterns have proven to be useful for broadening the debate about technical standards and as instructional tools. Your participation in this study will guide the development of a representation pattern library (http://lodlampatterns.org) that can be useful to Linked Data users, developers, students, and metadata creation professionals. Richard J. Urban, Assistant Professor College of Communication and Information School of Library and Information Studies Florida State University Florida's iSchool rurban at fsu.edu @musebrarian ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l at mcn.edu To unsubscribe or change mcn-l delivery options visit: http://mcn.edu/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://mcn.edu/pipermail/mcn-l/ -- *Richard Light*
[MCN-L] Using barcodes and tablets
On 30/05/2013 16:32, bryan kennedy wrote: The key here is that the QR code is equivalent to the URL and the URL is equivalent to the database entry for the thing. I think we're working to re-invent the URL sometimes. It's a great canonical identifier for things, as long as you remember Cool URIs don't change - http://www.w3.org/Provider/Style/URI.html . But this does require a develop for the web first mentality, which I understand is far from the norm in the collections management world. Excellent post, Bryan. I would strongly support the idea of using URLs as canonical identifiers. Interesting that you provide an updateable HTML view of the information, rather than a read only one. While no museum collection I know of has started off with URLs like yours for collections objects, it is possible to retro-fit a Linked Data view on to existing catalogue frameworks. Thus for example: http://collections.wordsworth.org.uk/Object/WTcoll/id/GRMDC.C104.4 is a persistent identifier for the Wordsworth Trust's object with accession/identity number GRMDC.C104.4. In addition, you can take advantage of content negotiation to get added value from this single identifier, so that it delivers you XML, RDF or even an image, via 303 See Other redirects to: http://collections.wordsworth.org.uk/Object/WTcoll/id/xml/GRMDC.C104.4 http://collections.wordsworth.org.uk/Object/WTcoll/id/rdf/GRMDC.C104.4 http://collections.wordsworth.org.uk/Object/WTcoll/id/jpeg/GRMDC.C104.4 respectively. Richard -- *Richard Light*
[MCN-L] websites from Mimsy
On 25/10/2011 02:53, lenore wrote: You might be interested, though, in a survey of the 200 or so AAMD websites that Willoughby has undertaken over the past 3 years. This survey has focused on the online access to collections offered by museums and, disappointingly, almost all of the online access to collections offered by these museums are replete with flaws, both conceptual and technological. If you'd like a copy of the report (which includes a critique of the problems as well as suggestions for improvements) -- it's scheduled for publication later this year or early next year -- please let me know. Lenore, I'm sure that the whole group would be interested in this report. Please tell the list when it's available. Do failure to publish as Linked Data and failure to tell stories feature in the critique? Best wishes, Richard -- *Richard Light*
[MCN-L] Database access for curators?
In message AANLkTikv88IgCKH20tsDA1YIfZHyEjcEfuQ98qeeYhWg at mail.gmail.com, Perian Sully perian at emphatic.org writes Likewise, I can't tell you how many times I've gotten into discussions with curators who want to delete the description field (used by registration for identification purposes) in favor of a more contextual, historical curated description. I have had to go into backups to restore the identifying description and re-incorporate it. These days, I'm in favor of a curator's description (or history, or curator's notes) field that the curators can use, in addition to a physical description field for the registration staff. Interesting how experience varies on this issue. I'm not sure whether it's a North America/U.K. difference, or simply one between larger museums who can afford to have IT staff to argue with the curators, and the sort of smaller museums I tend to deal with. Anyway, I agree that there is a distinction to be made between an identifying description, and one designed to bring out an object's cultural and/or historical significance. The latter is presumably destined for consumption by the public, and it would clearly be more helpful to include it, for example, in a summary record on your web site. In our Modes data structure we have gone a step further, and provided a repeatable Commentary element, each with a defined Audience. This allows multiple semi-structured descriptions of an object, each targeted at a specific sector of the public. This helps address the perennial problem of how museums can generate interesting web pages directly from the information held within their collections management system. Richard -- Richard Light
[MCN-L] image file names
In message AD775DE5635C2042BF1DCB7EED36A83B850A1D at jlm-net.jlm.local, Perian Sully psully at magnes.org writes Funnily enough, I was just about to draft up a file naming standards document and post it online. Other than some of the inherent difficulties with trying to align the digital filenames with the accession number (particularly when you don't have an accession number yet), what are some other arguments in favor of using a unique identifier instead of the accession number? One obvious argument is that it allows a single image to feature more than one object. Richard Light -Original Message- From: mcn-l-bounces at mcn.edu [mailto:mcn-l-bounces at mcn.edu] On Behalf Of Images Sent: Tuesday, June 08, 2010 12:03 PM To: Museum Computer Network Listserv Subject: [MCN-L] image file names We're reviewing how we name our image files and I'm hoping that some of you may have worked through this same issue. Currently, we use our accession number, however as this contains periods it has been identified as potentially problematic. For example, accession # 42.3.11 = VAG-42.3.11.jpg. One suggestion is to change the decimals to zeros but we are concerned that this makes the image file name difficult to read. Have any of you found a good solution to a problem like this? Any thoughts or samples of your naming structure would be most appreciated! thanks very much Danielle ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l at mcn.edu To unsubscribe or change mcn-l delivery options visit: http://toronto.mediatrope.com/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://toronto.mediatrope.com/pipermail/mcn-l/ ___ You are currently subscribed to mcn-l, the listserv of the Museum Computer Network (http://www.mcn.edu) To post to this list, send messages to: mcn-l at mcn.edu To unsubscribe or change mcn-l delivery options visit: http://toronto.mediatrope.com/mailman/listinfo/mcn-l The MCN-L archives can be found at: http://toronto.mediatrope.com/pipermail/mcn-l/ No virus found in this incoming message. Checked by AVG - www.avg.com Version: 9.0.829 / Virus Database: 271.1.1/2926 - Release Date: 06/08/10 19:35:00 -- Richard Light
[MCN-L] Jane Austen Manuscripts Online
In message 4BFE618E.2030603 at kcl.ac.uk, Tanner, Simon simon.tanner at kcl.ac.uk writes One of our CCH projects just went live: http://www.janeausten.ac.uk/index.html Thought you'd like it and want to share it. Interesting. You say: The project is therefore establishing the more advanced standards that will be adopted by the TEI for encoding the complexity of modern working manuscripts, in particular the temporal or genetic nature of these documents. Is further information available on your use of TEI? Richard -- Richard Light
[MCN-L] Google Apps
In message 747cfaf51003161530h6aa82e8aj27f8e5ee4cd14314 at mail.gmail.com, Ari Davidow aridavidow at gmail.com writes After using Google Apps and Google Docs for a couple of weeks on a specific project, I have to ask: Why on earth would anyone ever again spend a dime on Microsoft Office? Well, one response is that we have MS Office and everyone knows how to use it. Staff here have several times tried working with Google Apps (and with Zoho Apps, which seem better-featured and less buggy) and they hate 'em all. Hate the way the hosted apps track changes, hate the way they handle comments. This isn't true of all staff, but of enough, that this is still not an option for us. For us, at least, until hosted applications replace the way we currently do things with either a close functional equivalent, or something that people generally like better (and find easy to learn), it's still an ideal; not yet a realistic change. I came to the same conclusion some time ago, but with Open Office as the replacement software. It behaves in a manner which is closer to MS Office, and might be easier for the average user to switch to. Richard -- Richard Light
