To various lists
I thought I would share this extremely interesting tool created by Google for cataloging materials that are online, the “Structured Data Markup Helper” at http://support.google.com/webmasters/bin/answer.py?hl=en&topic=3070267&answer=3070230
This tool allows the webmaster of a page to add structured data to a page on their site. You put in the URL of the page to code or the HTML itself, and then you can simply highlight the areas that you want to code. It is based on the schema.org microdata and is very simple to do. I find the tool a little clunky and very incomplete but it is brand new. I tried coding my latest podcast, using the “Article” template. https://blog.jweinheimer.net/2013/04/cataloging-matters-no-19-library-catalogs-and-information-architecture.html and found it fairly simple, although I was unable to highlight the article body for some reason. I’ll probably use it on my next podcast.
As of now, the tags you can add for articles are very incomplete http://schema.org/Article and even lacks the vital “keywords” tag. When you are done, you download the HTML to your machine as microdata or as JSON-LD, and then add it to your page. When you upload it to your server, your page is ready to be “ingested” by Google or some other semantic technology that uses microdata and added to their data base where it can be manipulated. When Google adds recipes to the templates, people will be able to use this tool to tag their recipes, and then everyone can work with them, as I discussed in my latest podcast.
A raft of questions arise. Something like this may very well be the future interface of cataloging, and the question that arises in my own mind is: who will do the work? For this to work as it is intended, the metadata/microdata must be included in the page itself and is in a sense, a type of CIP. How would that work when a cataloger at another institution cataloged a page from, e.g. Ebsco? Also, could something like this be used to help trained catalogers do their work far more efficiently than they do today?
One additional point: for information on JSON-LD (linked data), there is an excellent video that describes pretty simply what JSON-LD is, but what I think is much more valuable, it shows the mind of a web developer: what concerns them and what does not concern them. https://www.youtube.com/watch?feature=player_embedded&v=vioCbTo3C-4 By the way, there are many who do not like JSON-LD but that should go without saying. 🙂