Example of authority control on messy data.

RDF-based. "Natural Collections Descriptions (NCD) covers all types of collections of natural history material; specimens, original artwork, photographs, archives, published material or a mixture."

Migration from one application to another is extremely time consuming because you are:

mapping from one set of entity types to another. Entities are the types of objects the application can hold (users/groups/documents/records/files/libraries/sites/retention rules etc)
mapping from one set of descriptive metadata fields to another
mapping from one set of functions to another. Functions are the actions that users can be permitted to perform on entities in the system (for example: create an entity/amend it/rename it/move it/copy it/delete it/attach a retention rule to it/grant or deny access permissions on it)
mapping from one set of roles to another. Roles are simply collections of functions, grouped together to make it easier to administrate them. For example in SharePoint the role of ‘member’ of a site collects together the functions a user needs to be able to access a site and view and download content, and to contribute new content to the site, but denies them the functions they would need to administer or change the site itself.

What's hard-to-parse about current-gen metadata, and how we can and can't make it better algorithmically. Not sure how I missed this one; it's fabulous.

Supposedly a MODS profile for research data coming soon.

Sad lack of actual documentation. Pity.

Includes PREMIS in METS validator, guidelines.

Fixing metadata (especially name metadata) led to FOUR TIMES the Google-referred hits for image collections. Whoa.

The OAI protocol facilitates the aggregation of large numbers of heterogeneous metadata records. In order to make harvested records useable in the context of an OAI service provider, the records typically must be filtered, analyzed and transformed. The CIC metadata portal harvests 450,000 records from 18 repositories at 9 U.S. Midwestern universities. The process implemented for transforming metadata records for this project supports multiple workflows and end-user interfaces. The design of the metadata transformation process required trade-offs between aggregation homogeneity and utility for purpose and pragmatic constraints such as feasibility, human resources, and processing time.

"Description of a Project:" metadata for software projects.

When they say "FGDC metadata," this is what they mean.

Definitions and distinctions for ontology, taxonomy, CV, etc.

<3 <3 <3. MARC name disambiguation, including some nasty edge cases, with Python.

CV for art description -- TEL grant

Why the LCSH is not a thesaurus. And things you never knew about doorbells.