We’re embarking on a project to adopt or build a metadata tool at Duke University Libraries. Before we’re immersed in architectures, designs, workflows, schedules, layers, platforms, capacities, etc., I’d like to indulge in some guilt-free big thinking. I thought I’d just kind of put the question out there: What are some of the big ideas that could inform the development of a metadata tool?
I invite conversation here and on the web4lib and code4lib lists, to which I’m sending an abridged version of this post. Other conversations will occur in various venues over the next month or so. I’ll try to pull together and post on anything I see, hear, read or say. In the meantime, I’ll share one big idea that I’ve been considering; I’m not saying it’s THE big idea or even implying that we’ll follow through on it at Duke. It’s just one way to bend our thinking about this project. I’m interested in other ideas that can help with the bending of the thinking on the project for the tool for the metadata.
The idea that I’m posing follows from a blog post that Lorcan Dempsey wrote in May, mentioning an example of a “shared cataloging environment”. When I read it, I wondered, what if you take that idea to its logical (illogical?) extreme: a metadata tool as a software-as-a-service (SaaS) platform.
Continue reading Grand Metadata Tool Ideas