I should have done this a long time ago. But, better late than never, as they say.
In the past, I interned at an archives to develop a digital archival collections management system. Having chosen to study rare books and manuscripts instead of archives during Library School, I spent a lot of time researching standards and procedures for archival collections management and development.
When I finally got down to the development phase, I knew enough to choose namespaces/elements for the metadata (to create fields which would be filled out when the metadata was added to cataloged objects). I knew the open source software I was customizing used Dublin Core, and I knew the basic requirements.
What still troubles me, is putting it all together. Which is where this post comes in. I have begun (again) to read about Dublin Core, and my goal for this post is to order the context and basics in my head, so I can move on from there to more fully understanding how Dublin Core affects and is used in metadata creation.
Dublin Core was established as a standard for “core metadata” that describes electronic resources simply and generically. The core comprises fifteen metadata elements:
I remember some of these from my archival internship, when I set up Dublin Core namespaces in CollectiveAccess.
The Dublin Core Metadata Initiative (DCMI) is now incorporated as a non-profit organization hosted at the National Library Board of Singapore.
Dublin Core terms Continue reading