One comment

  • Thanks to David for a great post. Again, well done.

    My feeling has always been to keep schemas clean and lean so as not to overwhelm the annotating users. In the discovery process we need to find the usual information that would normally be applied in asset documentation(job ticket). Users can then apply the most pertinent of those details to the asset during critical points of its lifecycle.

    Limiting the number of power users that upload assets, such as digital librarians or asset managers, is also important to help maintain the integrity of the system and the assets within. Asset documentation can be provide to these end users for final metadata review and input.

    Metadata fatigue can be a pitfall to a DAM. The metadata and schema planners may turn out to be only intermittent users making the system too cumbersome. Making annotation too complicated can lead to a user skipping fields or putting in wrong information just to get through the process. Key stakeholders, the end users should play an important part in the metadata and schema development.

    A search engine can only return the asset you make sure it can find.

    Frank Chagoya
    Leo Burnett USA

Leave a Reply

Your email address will not be published. Required fields are marked *