{"id":5467,"date":"2017-12-08T22:29:02","date_gmt":"2017-12-09T03:29:02","guid":{"rendered":"http:\/\/blogs.library.duke.edu\/bitstreams\/?p=5467"},"modified":"2017-12-08T22:14:26","modified_gmt":"2017-12-09T03:14:26","slug":"5467","status":"publish","type":"post","link":"https:\/\/blogs.library.duke.edu\/bitstreams\/2017\/12\/08\/5467\/","title":{"rendered":"Metadata Year-in-Review"},"content":{"rendered":"

As 2017 comes to a close and we gear up for the new year, I\u2019ve spent some time reflecting on the past twelve months. Because we set ambitious goals and are usually looking forward, not back, we can often feel defeated by all the work we haven\u2019t gotten done. So I was pleasantly surprised when my perusal of the past year\u2019s metadata work surfaced a good deal of impressive work. Here are a few of the highlights:<\/span><\/p>\n

Development and Dissemination of the DDR MAP<\/span><\/i><\/p>\n

Perhaps our biggest achievement of the year was the development of the DDR\u2019s very first formally documented metadata application profile, the <\/span>DDR MAP<\/span><\/a>. A metadata application profile defines the metadata elements and properties your system uses, documenting predicates, obligations & requirements, and input guidelines. Having a documented and shared metadata application profile promotes healthy metadata practices and facilitates communication. <\/span><\/p>\n

In addition to the generalized DDR MAP, we also developed a <\/span>Research Data Metadata Profile<\/span><\/a> and a <\/span>Digital Collections Metadata Profile<\/span><\/a> for those specific collecting areas.<\/span>\"\"<\/a><\/span><\/p>\n

Rights Management Metadata<\/span><\/i><\/p>\n

It\u2019s been written about on this blog a couple of times already (<\/span>here<\/span><\/a> and <\/span>here<\/span><\/a>) but I think it bears repeating: this year we rolled out a new rights management metadata strategy that employs the application of either a Creative Commons or RightsStatement.org<\/a> URI to all DDR resources, as well as the option of applying an additional free text rights note to provide context:<\/span><\/p>\n

\"\"<\/a><\/p>\n

We feel great about finally being able to communicate the rights statuses of DDR resources in a clear and consistent way to our end-users (and ourselves!).<\/span><\/p>\n

Programmatic Linking to Catalog Records<\/span><\/i><\/p>\n

Sometimes a resource in the DDR also has a record in the library catalog, and sometimes that record contains description that is either not easily accommodated by the DDR MAP, or it is not desirable to include it in the repository metadata record for a particular reason. It wasn\u2019t in the cards to develop a synchronization or feed of the MARC metadata, but we were able to implement a solution wherein we store the identifier for the catalog record on the resource in the repository, and then use that identifier to construct and display a link back to the catalog record.<\/span><\/p>\n

\"\"<\/a><\/p>\n

And Lots of Other Cool Stuff<\/span><\/i><\/p>\n

There were a lot of other cool metadata developments this year, including building out our ability to represent relationships between related items in the DDR, developing policies regarding the storage and display of identifiers, and a fancy new structural metadata solution for representing the hierarchical structure of born digital archives. We also got to work on some amazing new and revamped digital collections!<\/span><\/p>\n