Custom Tags for Bridge

Working within a news organization there can be many files and often times metadata can become an issue when dealing with so many files. Recently, I have been working on learning to code within XML. It was through this new skill that I was able to code these trial custom metadata panels for use in Bridge. Theoretically our student news organization at RIT could use these panels to more accurately tag their files.

An example of the code used below:

<xmp_definitions xmlns:ui=”http://ns.adobe.com/xmp/fileinfo/ui/”&gt;
<xmp_schema prefix=”spmetc” namespace=”http://spmetc.cias.rit.edu&#8221;
label=”$$$/AWS/FileInfoLib/Panels/spmetc/PanelName=spmetc”
description=”$$$/AWS/FileInfoLib/Panels/spmetc/PanelDescription=Custom metadata for spmetc”>
<!– simple properties –>

<!–This isn’t working correctly
<xmp_property name=”Status” category=”external” label=”$$$/Custom/Property/status_Label=Status:” type=”closedchoice” element_type=”text”>
<xmp_choice raw_value=”Unpublished” label=”$$$/Custom/Property/Choice_unpublished=unpublished”/>
<xmp_choice raw_value=”Published” label=”$$$/Custom/Property/Choice_published=Published”/>
</xmp_property>–>

<!–Use this–>
<xmp_property name=”event” category=”external” label=”$$$/Custom/Property/EventLabel=Event:”
type=”text”/>
<!– End of using this–>

<xmp_property name=”People” category=”external” type=”bag”
label=”$$$/Custom/Property/PeopleInput_Label=People:” element_type=”text” ui:multiLine=”true”
ui:height=”75″/>

</xmp_schema>
</xmp_definitions>

File Preservation of Digital Images

The troubles of file format preservation can be especially hard for such professions as photography. Photographers must deal with not only a lack of a hard copy of their work but also the issues of proprietary file formats with camera manufactures and image editing software. For example, the Nikon .NEF file used, as the company’s proprietary camera RAW file format will not even open in such systems as Adobe Bridge depending on the year the camera was produced and the version of .NEF file provided.

This could render collections of photographs useless. To help evade such issues the Digital Image Submission Criteria (DISC) standards have been provided by the IDEAlliance. The DISC standards recommend that of a JPEG high quality (level 8 ) and DNG a more universal RAW file format as delivery file formats (64).  These file formats are acceptable for file delivery but are they archival? This question can be answered by expanding upon our current knowledge of archival formats.

According to the Sustainability of Digital Formats Planning for Library of Congress Collections to be considered for archival status, certain aspects of the file must be measured. The first is disclosure; this means the amount of documentation that exists of over the created file (par 3). If it is an open source file format, there is more information than that of a proprietary allowing for the proper amount of information for a file to be properly preserved. Files are also measured on their adoption, if the format is widely used it allows for longer life in the digital world (par 7). Transparency “refers to the degree to which the digital representation is open to direct analysis with basic tools, including human readability using a text-only editor” (par 10).

Another factor is whether a file format allows for self-documentation through metadata, the idea being that if you can write within the file there may be clues on how to keep in an expectable condition for later use (par 16). It is also important to mention that external dependencies of the file type, if the file depends to much on specific hardware it may be tough to continue use if a digital system needs to be upgraded (par 20). Lastly, any patents and technical protection mechanisms must be considered to make sure that there is always access to the file and that multiple users are still able to obtain and work with it (par 22).

In regards to the DNG file format is considered to pass many of the requirements offered by the Library of Congress. “DNG is publicly documented, it is far more likely that raw images stored as DNG files will be readable by software in the distant future, making DNG a safer choice for archival” (Adobe Systems Incorporated 10). The public documentation of the metadata of the DNG file is also readily available allowing software to continue to read the files in the future (Adobe Systems Incorporated 10). As an extension of the TIFF 6.0 file format it is also compatible with the TIFF-EP standard and if necessary can “simultaneously comply” with the Digital Negative Standard as well (Adobe Systems Incorporated 10). This means that not only should file reader except a .DNG extension but also a .TIFF extension, opening up image storage into TIFF files as well (Adobe Systems Incorporated 11).

The color maintenance in the DNG file is rated to be excellent and allows for support of ICC profiles (Library of Congress par 4). This is very good when putting these files into a cross media workflow because it allows for the support and conversion of color profiles upon output. DNG also offers a way to create a standard way to encoder the raw sensor data from the camera and a few manufactures have begun to include DNG as an option for capture (OpenRAW Organization par 7). The format of the file is also intended for nondestructive image editing allowing for “for use with image manipulation tools that execute a variety of processes to transform the DNG into “pictures” suitable for different outputs” (Library of Congress par 4). Currently the compression of the image files is minimal when working with in the DNG format (Adobe Systems Incorporated 15). Transparency of the file is found only within the wrapper and any encoded data needs tools render (Library of Congress par 3).

Regarding the JPEG, file format is similar to the RAW in that it is fully disclosed and is documented by the Joint Photographic Experts Group (JPEG) (Library of Congress par 3). It has also been documented in the ISO standard in ISO/IEC 10918-1:1994 (JSTOR par 1). The transparency of the JPEG depends upon the type of software it does not have any external dependencies when it comes to reading or using the file (Library of Congress par 3). The file format has limited ability for technical metadata this would include such things as f-stop and aperture (Library Congress par 4). Color maintenance is limited and according to the Library of Congress does not support all ICC profiles.

The appeal of the JPEG file format that unlike DNG, the file format contains wide acceptance for digital capture and can be found in almost every camera or scanner as a capture option. However, even though the file format is available for capture it is not suggested due to the lossy compression when capturing data (Library Congress par 6). It should be noted that on some digital cameras there is an option for high quality jpeg. “It is using the same resolution as the RAW setting, assuring maximum image quality” (Smith par 5). Currently, Adobe Photoshop allows for JPEG and TIFF files to be opened and edited in the Camera Raw dialog (Adobe par 2).

Both the DNG and JPEG formats can be found to be file formats that are acceptable for long term preservation of files. However, it is important to note that each file has an appropriate place within the cross media workflow. The DISC standards make note that the DNG and JPEG are appropriate method of delivery and does not mention capture. However, if when capturing digital file formats it is important to use the highest quality possible so this maybe when a worker within the CMW uses a DNG file.

Due to the limited bit depth of the JPEG a DNG might also be best when editing images within the CMW. However, when a preview of an image is needed in the CMW a JPEG file with its compressed format would be ideal for fast loading time. Also if working with a website in a CMW a JPEG file format would be an excellent deliverable for such an output. It is important to note that were the final file will end up is the path it should follow within the CMW.

It is important to evaluate and migrate what is needed/wanted at least every five years when working with digital files (Gyor par 8). It is also important to pay attention to industry trends when working with files so that as formats fall out of favor the information they contain can be migrated over to a file format that allows for better preservation. By paying attention to what makes a file long lasting you are able to then extend the life of not only your files but the cross media workflows, content management systems and digital asset management systems that support it.

Extensis Portfolio vs. Xinet

Using both Portfolio and Xinet, in Digital Asset Management is interesting to reflect upon the ways that they are different representations of a DAM system.

Each DAM system varies in many different ways; the first way it varies is in the types of users Portfolio and Xinet providers for. Having used Portfolio first, I feel that this system is more aimed towards small or middle-sized companies. However it is expandable into larger companies such as the London Museum. Xinet, when initially opening it gives the impression of a larger system. It is more expansive and allows for use within a larger company.

In terms of metadata, the Xinet portfolio requires you to already add metadata prior to uploading to the server. Portfolio’s method of drag and drop metadata seems to me to be more user friendly and allows for easier adjustments to metadata. I understand why Xinet limits the addition of metadata because by making metadata more easily accessible like in Portfolio, you can run into standards problems. This also helps to control the vocabulary better than in portfolio, for this reason I believe that Xinet is more effective.

The interfaces are similar in that they both allow for preview icons with images and the option to display metadata next to each image or file. Portfolio’s interface is a lot cleaner and has a better navigation bar. I like that the navigation is easy to view as well as any action buttons. The overall aesthetic of Portfolio is reminiscent of a website and has amore stylized look to it. Xinet has a very plain interface and can sometimes be hard to navigate. I also don’t like the overall look of the Xinet it is very plain and the control buttons are very hard to see.

When controlling access to files in each system I feel that Xinet offers more security because you are allowed to make multiple user logins and expiration dates. Portfolio lacks this and I feel it would be a nice addition to the software. I also prefer the way you can access originals in Xinet through a server. I feel that this allows for more security when controlling original asset changes. I’m not aware that this is allowed in Portfolio. I wish Portfolio had the drag and drop from their website like Xinet, I would really like to see this feature added as well.

While I prefer the idea of Xinet, the installation process and set up is very long and labor intensive. For this reason I feel Portfolio is the better choice when it comes to more easily implementing it within a company. Also Portfolio is considerably cheaper than Xinet. I think that this will really play a part in which DAM system a person would chose for their company.

Taxonomy of Keywords & Their Importance

As the world becomes increasingly digitized, there is a new need for standardization of digital media files. The ways in which these files are stored are important, but even more so are the ways in which metadata is applied to allow one to search for a file once it has been placed within a content management system.

While looking at metadata standards, it is important to think about image capture standards as well. Images, especially those captured digitally, must meet certain criteria in order to be stored over a period of time, as well as allow for multiple uses. One example of image capture standards is the Digital Image Submission Criteria (DISC) standards provided by the IDEAlliance. DISC gives advice on how to store images for maximum reproduction in print and other media, while also lending itself to proper archival storage of digital images and files.

The DISC standards allow for digital media creators and publishers to deal with common problems found within a digital workflow. By following image standards, the digital file creator is able to determine the minimum quality level for digital images for printed output. Such standards also provide a way of creating a contract between the creator of the file and the acceptor, by creating guidelines specifying how images will be accepted or rejected. The DISC surveys also determine what format images should be submitted in. For example, in our Xinet project it was determined that images would be submitted as tiff files, using LAB color space and be at least 8 bit depth. A final aspect is how images should be labeled so that they fit within the digital workflow. This allows the image takers to create a standard to reach towards when outputting their work to the collective (Dougherty 2).

When images are rejected, it is understood that it is because the files did not meet the requirements laid out by the image standards. It is common for photographers and other digital file creators to not even receive payment for their work in the digital workflow world if their files do not follow the standards set forth by the receiving digital workflow. In a way, standards for image capture serves as a contract for both parties involved in the digital workflow.

Metadata is often utilized within the DISC standards. One aspect of metadata is the use of keywords to allow files to be searched. An important part of this includes the use of keywords. Keywords are part of an access structure, which “relates content types or publication pages to each other or to an external set of concepts that can be used to get to a particular content type” (Boiko par 40). Keywords fall within the indexing structure of metadata in the ranking of access structures making it the one of the most important fields. Keyword entry may come in different forms, for example in the IPTC Core, in which there is a spot for keywords. Similarly, within some museum systems there is a “Subject Matter—Description…A description of the work in terms of the generic elements of the image or images depicted in, on, or by it,” which may also hold keywords (Harpring par 10).

It is important when using keywords that taxonomy is applied to them. Since keywords may be free text, it is important to have a standard when using them (Dougherty 6). Taxonomy allows for  “an orderly classification that explicitly expresses the relationships, usually hierarchical (e.g., genus/species, whole/part, class/instance), between and among the things being classified” (Gill par 80). It is also important to keep in mind that many times keywords are known as open lists so you must “make sure that you trust users to add new items responsibly” (Boiko 10). When creating keywords, you must keep in mind the result – an extensible series of categories for organizing digital assets into meaningful sets (Bock 4).

“Using a taxonomy, we know how to relate one term in the information hierarchy to another” (Bock 5). If we look at this from the perspective of a cataloger of an art museum, it may take place in three steps. The first is where keywords entered may be generic, such as “nude” or “woman”, which are elements that would be easily observable to any person that is viewing the work. The next level would be identification, providing information that is generally more specific, such as “Birth of Venus.” Finally, the last set of keywords would deal with an even more specific set of terms that allow for interpretation, for example “Sandro Botticelli Classiest representation of Venus Birth” (Harpring par 20).

In respect to my experience with Xinet for a classproject, the keywords were chosen in a similar fashion to the hierarchy described in Introduction to Art Image Access, Issues, Tools, Standards, and Strategies. The first level of keywords for the images represents an overall knowledge of the subject matter. For example, the topic chosen for the images was baked goods, so the first keyword to be entered was “food” since this is a general term for anything editable (and the baked goods are food). Next, a keyword identifying the type of food was added – bakery. Since the baked goods came from a specific store, it was also added so that someone searching for the bakery name would be able to find it, along with “menu” to denote that this may be found year round in their store. In addition, “sweets” was added to show the type of baked good in the photo. Finally, the specific name of the baked good was added, “vanilla bean slice”.

It is important to use taxonomy within any type of database when dealing with digital media, as it allows users of all occupations and knowledge bases to easily search for images in a timely manner while preserving the original intent of the digital media.

 

References:

 

Bock, G. E. (2005, October). Designing Metadata An Implementers Guide for Organizing and Using Digital Assets. Bock and Company, 1, 21.

 

Boiko, Bob. (2005). Content management bible, 2nd edition.

[Books24x7 version] Available from.

 

Dougherty, J., & Lam, K. w. (2007, May). DISC 2007 Specifications and Guidelines. Graphic Arts Monthly, 1, 9.

 

Gill, T., Gilliland, A. J., Whalen, M., & Woodley, M. S. (n.d.). Introduction to Metadata (Research at the Getty). The Getty. Retrieved January 1, 2011, from web.

 

Layne, S. S., Harpring, P., Hourihane, C., & Sundt, C. L. (n.d.). Introduction to Art Image Access (Research at the Getty). The Getty. Retrieved January 1, 2011, from web.