Re: [CODE4LIB] Inquiry about Omeka developers
Please forgive the double-posting, but wanted to give a last reminder that the Omeka team wants to learn more about who Omeka devs are, where they are, what they're doing, and -- most importantly -- how we can help your work. Original message is below. TL;DR: There's a survey asking Omeka devs at http://omeka.org/blog/2016/02/02/who-are-our-omeka-developers So far, 13 countries in 4 continents (come on Africa and Asia! Antarctica would be awesome) are represented by librarians, developers, CTOs, archaeologists, analysts, sysadmins, freelancers and more. We want to hear from as many coders, at any level, before we start studying results on February 19. Thanks, all. Patrick Murray-John Omeka Director of Developer Outreach On 02/02/2016 03:29 PM, Patrick Murray-John wrote: In the past few years, we have been delighted to see more and more developers of both themes and plugins contacting us on our href="https://groups.google.com/forum/#!forum/omeka-dev;>developer list and on the http://omeka.org/forums/;>forums. That has made us curious about who all of you are, and what can we do better to help you. With that in mind, we've put together a short survey to get to know you better. It'll take about ten minutes. We're asking about where you are, what kinds of places you work for, and what kinds of Omeka development you do. We'll use this information to guide our documentation and outreach efforts. Personal information, of course, will not be exposed or sent to others. We'd like to hear about any level of Omeka development, from building a plugin to hacking a couple lines of a theme. All those activities are important to us, and knowing about the people and projects that spur the activity will help tremendously. Please fill out and share href="http://goo.gl/forms/of19fFALqJ;>the survey if you have written or hacked Omeka code. We'll start compiling and analyzing the data on February 19, so responses before then are much appreciated. Many thanks, Patrick Murray-John Director of Omeka Developer Outreach
[CODE4LIB] Inquiry about Omeka developers
In the past few years, we have been delighted to see more and more developers of both themes and plugins contacting us on our href="https://groups.google.com/forum/#!forum/omeka-dev;>developer list and on the http://omeka.org/forums/;>forums. That has made us curious about who all of you are, and what can we do better to help you. With that in mind, we've put together a short survey to get to know you better. It'll take about ten minutes. We're asking about where you are, what kinds of places you work for, and what kinds of Omeka development you do. We'll use this information to guide our documentation and outreach efforts. Personal information, of course, will not be exposed or sent to others. We'd like to hear about any level of Omeka development, from building a plugin to hacking a couple lines of a theme. All those activities are important to us, and knowing about the people and projects that spur the activity will help tremendously. Please fill out and share href="http://goo.gl/forms/of19fFALqJ;>the survey if you have written or hacked Omeka code. We'll start compiling and analyzing the data on February 19, so responses before then are much appreciated. Many thanks, Patrick Murray-John Director of Omeka Developer Outreach
[CODE4LIB] DPLA Ada Lovelace Day 2015
Apologies for Cross-postings. Please share widely if so inclined! We want to invite you to get involved with the DPLA Ada Lovelace Day, a coordinated, multi-community event happening on October 13, 2015. The goal of this day is to inspire and guide simultaneous DPLA Ada Day events in different communities and cities on Ada Lovelace Day. The simultaneous events will celebrate the life and work of Ada Lovelace by using the DPLA digital collections and related tools to make women in technology, science and mathematics apps, projects, syllabi, essays, digital exhibitions or anything else in the spirit of Ada Lovelace day. We welcome anyone and everyone to organize a DPLA Ada Lovelace Day event in your own area; these can be hackathons, workshops, or any other event permutation, with the shared focus on women in technology, science, and mathematics highlighted by working with the DPLA collections. To coordinate, a list of events being planned will be available on the DPLA Ada Lovelace Day site. Additionally, at the end of the day, communities’ creations and responses to the event will be shared on this site. See more information there: http://dpladalovelace.us/
Re: [CODE4LIB] Code4lib DMV 2015 | Call for proposals
Is it best process to ask for an account on the wiki from the email that's on the login page? Patrick On 07/14/2015 11:55 AM, Francis Kayiwa wrote: This year, code4libDMV is being hosted in College Park, MD on August 11th and 12th. The conference is open to anyone to attend and we encourage those who live close to do so. This email is serves as an invitation for those in the area to submit the cool things you are doing this summer or the problems you would like to flesh out with your peers. http://wiki.code4lib.org/MDC The programming team will try and find a home for as many sessions as possible. If you have questions -- let me know. Cheers, ./fxk
Re: [CODE4LIB] Fedora 4 repositories with open API?
Esmé, Thanks. I've got my own going okay, and the basics seem to work. The next step, as always, is seeing what happens with real live data, rather than the minimal test data I have in there. Live-fire data, I find, exposes more and more unanticipated quirks! Patrick On 07/08/2015 04:27 PM, Esmé Cowles wrote: And if there aren't any open Fedora 4 repositories forthcoming, you can always use fcrepo4-vagrant to spin up your own pretty easily: https://github.com/fcrepo4-labs/fcrepo4-vagrant -Esme On 07/08/15, at 4:01 PM, Tom Cramer tcra...@stanford.edu wrote: Hi Patrick, To my knowledge, Penn State has one of the current Fedora 4 repositories in production; a few others are close (including the Royal Library of Denmark). You might also want to post th is query on the fedora-t...@googlegroups.com and/or fedora-commun...@googlegroups.com list. Hope this helps, - Tom PS. Has there been any thought that Omeka S might also be IIIF-friendly http://iiif.io/, and able to present image-based resources from any IIIF-compatible repository by consuming both the IIIF image and presentation APIs http://iiif.io/technical-details.html? I can muster up some live IIIF API endpoints, if you are interested. On Jul 8, 2015, at 9:07 AM, Patrick Murray-John patrickmjc...@gmail.com wrote: Hi all, The Omeka http://omeka.org web publication tool for GLAMs is working on a new version, Omeka S, that will include modules for connecting to various other systems, including Fedora 4. Does anyone have a Fedora 4 installation with open API that we could use to test the basic reading and import mechanisms against? This would be for development and testing purposes only. Many thanks, Patrick Murray-John Omeka Director of Developer Outreach
Re: [CODE4LIB] Fedora 4 repositories with open API?
Tom, Many thanks. I'll look there, and also look to those groups. Thanks for the tip! On the IIIF question, yep! It's on our mind: https://github.com/omeka/omeka-s/issues/182 Patrick On 07/08/2015 04:01 PM, Tom Cramer wrote: Hi Patrick, To my knowledge, Penn State has one of the current Fedora 4 repositories in production; a few others are close (including the Royal Library of Denmark). You might also want to post th is query on the fedora-t...@googlegroups.com and/or fedora-commun...@googlegroups.com list. Hope this helps, - Tom PS. Has there been any thought that Omeka S might also be IIIF-friendly http://iiif.io/, and able to present image-based resources from any IIIF-compatible repository by consuming both the IIIF image and presentation APIs http://iiif.io/technical-details.html? I can muster up some live IIIF API endpoints, if you are interested. On Jul 8, 2015, at 9:07 AM, Patrick Murray-John patrickmjc...@gmail.com wrote: Hi all, The Omeka http://omeka.org web publication tool for GLAMs is working on a new version, Omeka S, that will include modules for connecting to various other systems, including Fedora 4. Does anyone have a Fedora 4 installation with open API that we could use to test the basic reading and import mechanisms against? This would be for development and testing purposes only. Many thanks, Patrick Murray-John Omeka Director of Developer Outreach
[CODE4LIB] Fedora 4 repositories with open API?
Hi all, The Omeka http://omeka.org web publication tool for GLAMs is working on a new version, Omeka S, that will include modules for connecting to various other systems, including Fedora 4. Does anyone have a Fedora 4 installation with open API that we could use to test the basic reading and import mechanisms against? This would be for development and testing purposes only. Many thanks, Patrick Murray-John Omeka Director of Developer Outreach
Re: [CODE4LIB] Automated Embedded Metadata Extraction in Photographs: Possible or Pipedream?
The extraction and ingestion seem like two different coins. Lots of tools can extract. exiftool, or imagemagick, or whatever can extract the data. Question then is how and where to insert it into the system you are using. So, not a pipedream. Indeed extraction is very possible. The harder part might be figuring out how or where to store the data in your system. Then, assuming it's relevant, how/where your system actually displays or uses the data. Depending on your system, that's where the pipedream question comes into play, I think. Patrick On 12/17/2013 04:45 PM, Kyle Banerjee wrote: Exiftool is what you need. Easy to use and works on any platform. kyle On Tue, Dec 17, 2013 at 1:37 PM, Swauger,Shea shea.swau...@colostate.eduwrote: Hi all, I'm wondering if there is a systematic method that can extract metadata embedded in digital photographs and then ingest that metadata into a CMS and relate them to their corresponding images. We currently use DigiTool, if that makes a difference. Thanks! Shea Swauger Data Management Librarian Colorado State Univeristy
[CODE4LIB] Request for help via a survey
Hi all, I'm writing to ask any of you who work in a museum or other exhibiting institution for take a 5 minute survey (or pass it on to whomever you think might be interested). It will help with some planning as we explore some new directions in development: https://www.surveymonkey.com/s/BDZHQKM Thanks, Patrick
Re: [CODE4LIB] RDF advice
Ethan, The semantics do seem odd there. It doesn't seem like a skos:Concept would typically link to a metadata record about -- if I'm following you right -- a specific coin. Is this sort of a FRBRish approach, where your skos:Concept is similar to the abstraction of a frbr:Work (that is, the idea of a particular coin), where your metadata records are really describing the common features of a particular coin? If that's close, it seems like the richer metadata is really a sort of definition of the skos:Concept, so maybe skos:definition would do the trick? Something like this: ex:wheatPenny a skos:Concept ; skos:prefLabel Wheat Penny ; skos:definition Your richer, non RDF metadata document describing the front and back, years minted, etc. In XML that might be like: skos:Concept about=http://example.org/wheatPenny; skos:prefLabelWheat Penny/skos:prefLabel skos:definition Your richer, non RDF metadata document describing the front and back, years minted, etc. /skos:definition /skos:Concept It might raise an eyebrow to have, instead of a literal value for skos:definition, another set of structured, non RDF metadata. Better in that case to go with a document reference, and make your richer metadata a standalone document with its own URI: ex:wheatPenny skos:definition ex:wheatPennyDefinition**.xml skos:Concept about=http://example.org/wheatPenny; skos:definition resource=http://example.org/wheatPenny.xml; / /skos:Concept I'm looking at the Documentation as a Document Reference section in SKOS Primer : http://www.w3.org/TR/2009/NOTE-skos-primer-20090818/ Again, if I'm following, that might be the closest approach. Hope that helps, Patrick On 02/11/2012 09:53 PM, Ethan Gruber wrote: Hi Patrick, The richer metadata model is an ontology for describing coins. It is more complex than, say, VRA Core or MODS, but not as hierarchically complicated as an EAD finding aid. I'd like to link a skos:Concept to one of these related metadata records. It doesn't matter if I use skos, owl, etc. to describe this relationship, so long as it is a semantically appropriate choice. Ethan On Sat, Feb 11, 2012 at 2:32 PM, Patrick Murray-John patrickmjc...@gmail.com wrote: Ethan, Maybe I'm being daft in missing it, but could I ask about more details in the richer metadata model? My hunch is that, depending on the details of the information you want to bring in, there might be more precise alternatives to what's in SKOS. Are you aiming to have a link between a skos:Concept and texts/documents related to that concept? Patrick On 02/11/2012 03:14 PM, Ethan Gruber wrote: Hi Ross, Thanks for the input. My main objective is to make the richer metadata available one way or another to people using our web services. Do you think it makes more sense to link to a URI of the richer metadata document as skos:related (or similar)? I've seen two uses for skos:related--one to point to related skos:concepts, the other to point to web resources associated with that concept, e.g., a wikipedia article. I have a feeling the latter is incorrect, at least according to the documentation I've read on the w3c. For what it's worth, VIAF uses owl:sameAs/@rdf:resource to point to dbpedia and other web resources. Thanks, Ethan On Sat, Feb 11, 2012 at 12:21 PM, Ross Singerrossfsin...@gmail.com wrote: On Fri, Feb 10, 2012 at 11:51 PM, Ethan Gruberewg4x...@gmail.com wrote: Hi Ross, No, the richer ontology is not an RDF vocabulary, but it adheres to linked data concepts. Hmm, ok. That doesn't necessarily mean it will work in RDF. I'm looking to do something like this example of embedding mods in rdf: http://www.daisy.org/zw/ZedAI_**Meta_Data_-_MODS_** Recommendation#RDF.2FXML_2http://www.daisy.org/zw/ZedAI_Meta_Data_-_MODS_Recommendation#RDF.2FXML_2 Yeah, I'll be honest, that looks terrible to me. This looks, to me, like kind of a misunderstanding of RDF and RDF/XML. Regardless, this would make useless RDF (see below). One of the hard things to understand about RDF, especially when you're coming at it from XML (and, by association, RDF/XML) is that RDF isn't hierarchical, it's a graph. This is one of the reasons that the XML serialization is so awkward: it looks something familiar XML people, but it doesn't work well with their tools (XPath, for example) despite the fact that it, you know, should. It's equally frustrating for RDF people because it's really verbose and its syntax can come in a million variations (more on that later in the email) making it excruciatingly hard to parse. These semantic ontologies are so flexible, it seems like I *can* do anything, so I'm left wondering what I *should* do--what makes the most sense, semantically. Is it possible to nest rdf:Description into the skos:Concept of my previous example, and then placenuds:nuds.more sophistated model../nuds:nuds into rdf:Description (or alternatively, set rdf:Description/@rdf:resource
Re: [CODE4LIB] RDF advice
Ethan, Maybe I'm being daft in missing it, but could I ask about more details in the richer metadata model? My hunch is that, depending on the details of the information you want to bring in, there might be more precise alternatives to what's in SKOS. Are you aiming to have a link between a skos:Concept and texts/documents related to that concept? Patrick On 02/11/2012 03:14 PM, Ethan Gruber wrote: Hi Ross, Thanks for the input. My main objective is to make the richer metadata available one way or another to people using our web services. Do you think it makes more sense to link to a URI of the richer metadata document as skos:related (or similar)? I've seen two uses for skos:related--one to point to related skos:concepts, the other to point to web resources associated with that concept, e.g., a wikipedia article. I have a feeling the latter is incorrect, at least according to the documentation I've read on the w3c. For what it's worth, VIAF uses owl:sameAs/@rdf:resource to point to dbpedia and other web resources. Thanks, Ethan On Sat, Feb 11, 2012 at 12:21 PM, Ross Singerrossfsin...@gmail.com wrote: On Fri, Feb 10, 2012 at 11:51 PM, Ethan Gruberewg4x...@gmail.com wrote: Hi Ross, No, the richer ontology is not an RDF vocabulary, but it adheres to linked data concepts. Hmm, ok. That doesn't necessarily mean it will work in RDF. I'm looking to do something like this example of embedding mods in rdf: http://www.daisy.org/zw/ZedAI_Meta_Data_-_MODS_Recommendation#RDF.2FXML_2 Yeah, I'll be honest, that looks terrible to me. This looks, to me, like kind of a misunderstanding of RDF and RDF/XML. Regardless, this would make useless RDF (see below). One of the hard things to understand about RDF, especially when you're coming at it from XML (and, by association, RDF/XML) is that RDF isn't hierarchical, it's a graph. This is one of the reasons that the XML serialization is so awkward: it looks something familiar XML people, but it doesn't work well with their tools (XPath, for example) despite the fact that it, you know, should. It's equally frustrating for RDF people because it's really verbose and its syntax can come in a million variations (more on that later in the email) making it excruciatingly hard to parse. These semantic ontologies are so flexible, it seems like I *can* do anything, so I'm left wondering what I *should* do--what makes the most sense, semantically. Is it possible to nest rdf:Description into the skos:Concept of my previous example, and then placenuds:nuds.more sophistated model../nuds:nuds into rdf:Description (or alternatively, set rdf:Description/@rdf:resource to the URI of the web-accessible XML file? Most RDF examples I've looked at online either have skos:Concept or rdf:Description, not both, either at the same context in rdf:RDF or one nested inside the other. So, this is a little tough to explain via email, I think. This is what I was referring to earlier about the myriad ways to render RDF in XML. In short, using: skos:Concept about=http://example.org/foo; skos:prefLabelSomething/skos:prefLabel ... /skos:Concept is shorthand for: rdf:Description about=http://example.org/foo; rdf:type resource=http://www.w3.org/2004/02/skos/core#Concept; / skos:prefLabelSomething/skos:prefLabel /rdf:Description So, yeah, you use one or the other. That said, I'm not sure your ontology is really going to work well, you'll just have to try it. One thing that would probably be useful would be to serialize out a document with your nuds vocabulary as rdf/xml and then use something like rapper (comes with the redland libraries) to convert it to something more RDF-friendly, like turtle, and see if it makes any sense. For example, your daisy example above: rdf:RDF xmlns:rdf=http://www.w3.org/1999/02/22-rdf-syntax-ns#; xml:mods=http://www.daisy.org/RDF/MODS; rdf:Description rdf:ID=daisy-dtbook2005-exemplar-01 mods:titleInfo mods:titleWorld Cultures and Geography/mods:title /mods:titleInfo mods:name mods:namePartSarah Witham Bednarz/mods:namePart mods:role mods:roleTerm mods:type=textauthor/mods:roleTerm /mods:role /mods:name mods:name mods:namePartInés M. Miyares/mods:namePart mods:role mods:roleTerm mods:type=textauthor/mods:roleTerm /mods:role /mods:name mods:name mods:namePartMark C. Schug/mods:namePart mods:role
