Embracing the enormity of metadata challenges in Scholarly Communications through Community Group discussions. Metadata 2020 has always had big goals. From the earliest conversations between Metadata 2020 Director Ginny Hendricks and the Advisory Group she quickly convened, it was clear that there were a number of different directions a collaborative effort could take to improve metadata scholarly communications, the possibilities were seemingly endless. How, then, to narrow the scope and organize efforts?
Following the launch of Metadata 2020 at the beginning of September, we have been delighted to receive many enquiries from individuals across scholarly communications who are eager to participate in the collaboration. The support is also clear through Twitter conersations. Thank you to all of you who have offered your help! As a result of the interest received, we have been able to start to form a variety of Community Groups for Publishers, Librarians, Researchers, Funders, Service Providers/Platforms and Tools, and Data Publishers/Repositories.
Writing a blog post ‘about metadata’ is like calling a paramecium ‘a hungry slipper with fringe’ - you’re bound to miss out on a lot of detail. Metadata is the thing I got my library degree for, mostly because I think metadata is fascinating, but also because I loathed the reference desk and wanted regular hours. However, as my career went on (and on), I found the issues around metadata to be increasing as the supposed ease of discovery through electronic means became more universal.
I’ve been thinking and talking about Metadata 2020 for well over a year now, and we’ve run lots of workshops and met several times with a team of advisors, so this is a bit of a weird post to write. (And a bit nerve-wracking now we’re making it official - there’s even a news release about the launch!) But here we are with three or four events under our belts and more planned, numerous interviews giving clear insights, dozens of supporters with plans for thousands, and some very ambitious goals: