|
|
|
Elements to Consider in Planning Your ProjectMission and Scope of the Project: You should consider the purpose and audience of the project and the information to be conveyed to that audience. Developing written policies that address these issues will help focus the project in your mind and help ensure that everyone involved has a common understanding of the project. The policies can be used as a "reality check" by soliciting input from project staff, administrators, users, and others.It is not essential to spend a great deal of time on these policies, especially when an organization is developing its first digital project or Website, or a new collection of pages for an existing site. These policies should be modified as the project evolves and as you acquire more experience with how the project can meet your organization's needs. Policies on mission and scope of the project should consider the following: What Are Your Goals? What do you want the project to accomplish? Are you expanding outreach, improving access to a wider audience that can't easily come to your site or can't come during your regular hours? Do you want to improve preservation of the materials by reducing handling of originals? How do your project goals fit into your organization's larger strategic plan? Who Will Use The Information? It is important to design for your intended audience and keep their needs in mind as you plan and develop your project. Will they be educators, students, researchers, family historians, the general public, etc.? Do not forget the purpose of your project is to communicate with your audience. Effective project plans are based on answers to questions about your audience such as: How Will They Use The Information? What kind of information will the users want, and how will they want it packaged? How much do they know about the organization of library collections, museums, or archives? Will they phrase general or specific research questions? What are their computer and Internet skills? Do they need a lot of explanation and help, are they sophisticated users, or both? What are the users' computer resources? What Resources Are Available? Acquiring the hardware and software for the system is only one portion of the process. Preservation of original materials after digitizing, managing back-up files, description and cataloging take time and effort, as do the design and development of your project. Estimates of time project that two hours of technology staff or maintenance may be required for every hour devoted to the preparation of an online digital library. Some estimates range as high as 20 to 1! In creating your original plan, offer a realistic estimate of the time required per image file to house, accession, scan, resize, create a catalog record and apply the file to your system. Plan for long term maintenance and eventual migration of your digital files. Don't assume existing resources devoted to an off-line equivalent will be able to absorb the additional work to support the Web service. On-line access to collections can significantly increase requests for research assistance, reproductions of photographs and other services. Who Will Do The Work? Photographic experience is very helpful in learning to scan and adjust image files. Likewise, librarians, archivists, and curators have experience helpful in composing cataloging records (called metadata). Technical support and screen design are other specialized skills helpful for successful projects. If more than one person works on the project, it is essential that staff work closely together from the initial planning. Also, cataloging and digitizing are labor intensive and may require a skill level above that of minimum wage employees. If your current staff does not have the necessary skills, training should be included in the planning. Who Is Responsible For The Project? As noted above, any large project will have many people working together. Ultimately, one individual must be designated to manage the project and make final decisions. This individual should have a strong grasp of the mission and scope of the entire project and an understanding of technological aspects, information organization, and interface design. How Will Users Gain Access? Will your system be for in-house use by patrons and staff or will you make material available on the Web? Issues such as cultural sensitivity and copyright become especially important when image files are posted to the Web. In-house use generally considered "Fair Use" within your institution may not be "Fair Use" outside of your institution on the Web. Design questions include: How will you protect your files from being downloaded off the Web, or do you care? What software will you use? Who will create and maintain the in-house system and/or Website? Decisions about file size will be influenced by how your users will get access to the information. For example, small file sizes take less time to load and are preferred if your users use modems. Copyright Issues, Who Owns The Rights? Generally, the law provides that a published item is protected under copyright for at least 75 years, unless produced by a government entity or unless the rights are transferred. Copyright remains with the producer of the item, his/her descendants, or designee, such as a publisher or employer, and must be transferred in writing. Unpublished material and that published after January 1, 1923, is protected under current copyright law and you should only reproduce such material with permission of the copyright holder. Donor agreements should include transfer of rights for unpublished material, and published material produced after January 1, 1923. If you are not certain about your institution's rights to publish an item, you should verify ownership and permissions before doing so. What Material Will You Digitize? The size and physical conditions of the items will help decide what equipment and software will be necessary for your project. Photographs and fragile documents will require much more staff time and possibly specialized software, such as Photoshop, compared to printed items of a uniform size which might be able to be form fed. Grouping material can save significant time later in the project. You will also need to decide how you plan to digitize your collections: the most popular collections first, everything in a collection, regardless of value of specific items, or a representative sampling from many collections. Preservation: After scanning it is important to correctly house and store your original, paper or source material, according to standard preservation practices. A good digitization program provides an excellent opportunity to preserve and maintain the original as a part of its plan. Photographs, documents, and artifacts can be properly rehoused, accessioned and stored in an improved environment. Generally this adds little to the cost of the project, and will add to the life of the collection. Preservation of original material is required in all projects supported by our Agency. What Physical Facilities Are Available? Scanning projects require adequate space for computers, scanning devices, printers, peripherals, people and preservation, even if there is only one person working on the project. Plan for an appropriate amount of space in an environmentally appropriate location. How Will You Store And Maintain The Information? The most popular current options are tape, compact disc and on a fixed disc. If you choose to store your image or text files on a hard drive store the files in formats recommended in the Agency guidelines. Plan for adequate back-up of data files, and for sufficient storage space for file servers if material will be available on the Web. Describing and Cataloging Your Materials Using the Dublin Core FormatThe combination of digital information, computers, and the Internet/Web in the coming years provides amazing new opportunities for Arizona’s cultural and historical institutions. Every citizen of the state, as well as many beyond, will increasingly be able to view the unique artifacts, documents, writings, photographs and maps held by the various museums, archives and libraries in Arizona and throughout the world. In order to coordinate access to the collections in many institutions, these online resources will need to be created (scanned or digitized), indexed, organized and maintained in systems which are able to work together. The goal is to provide the same access to anyone, wherever they may be - Tuba City, Phoenix or Sierra Vista. Special vocabulary, called nomenclature, exists to help create metadata. It builds on a shared structure and vocabulary guide describing library, archives or museum items or collections. You will need to organize the information about each item that you digitize into a database to provide access and permit searching. Representatives from libraries, archives, and museums and many other professions have created a brief list of 15 common universal cataloging elements to permit sharing across collections. This list of cataloging fields is called the Dublin Core. At its simplest it is a system that creates the indexes that work together. Almost every museum artifact, archival document, photograph, or publication can fit into some of these categories. The system has been designed for international use of a broad range of disciplines, such as government, the sciences, social sciences, humanities, and business. Our agency has developed a template consistent with the Dublin Core guidelines that provides the minimum amount of information required to describe and catalog each item that you digitize. Descriptive information about the item that will be of interest to the patron, such as title, description, and format, will be organized into categories consistent with the Dublin Core cataloging standards. All Dublin Core fields are repeatable, if necessary, to adequately describe your collection. For example: you may choose to list more than one subject heading. We recommend the following Dublin Core fields be mandatory in your database creation: Title, Identifier, Publisher, Creator, Date, Subject, Description, and Type. The remaining fields are optional and can be used if your needs require this information. Administrative information about the digital file itself - the date digitized, digital formats, etc. - will also be required if you maintain digital formats and has been included in the template. If desired, additional information about each item or collection can be included on your database. If your catalog already exists in a structured database which follows established standards, it may be possible to create electronic links to the Dublin Core to eliminate re-entry of data. This process is called creating a "crosswalk" or link from your catalog field to the Dublin Core field for searching and retrieval. Crosswalk formats are currently being developed nationally, and may not be immediately available for you to implement. A sample crosswalk for the Arizona State Library, Archives and Public Records is listed in Attachment 7. Take your time. Be thorough when describing and creating the items. The more description you give (for instance, all of the people in a photograph), the more valuable your information will be. Think creatively. A patron once asked us for pictures of hats—we had never cataloged "hats" in our database, but we watch for them now. Aspects that seem bizarre or unusual, like mesquite fences and peculiar shoes, as well as George Hunt’s spittoon in a photograph, can be a treasure to a particular researcher. On the other hand it is very time consuming and unwise to minutely over-describe an object or collection. Balance and good judgment are essential skills in the art of cataloging. Above all, have fun! Looking closely at the treasures in your collection will not only provide better databases, but it will also make the experience more enjoyable.
Dublin Core Note: White boxes denote mandatory fields.
Digital File Data
Examples of other possible administrative data for inclusion in your database (but for public access)
Dublin Core Type Definitions
The Type category may be repeated as necessary to include different categories. Examples are multimedia resources, which should include each appropriate category: and collections, which should include the heading "collection" and any other appropriate type(s) (e.g. "text", "image", etc.). For additional information on the Type category see http://lcweb.loc.gov/marc/dc/typequalif-19991210.html Database Selection and OrganizationIn the simplest terms, a database is an index. It is a tool, such as a catalog, which enables researchers to find what they seek. The magic of a database is that it can allow sorting information many ways. If your collection includes photographs, brass items, and campaign buttons, it could be sorted to find all the items you have about Barry Goldwater’s presidential campaign, or all the photographs you have of Paul Fannin (even if it’s on a photograph featuring somebody else), or all the items created in 1964. Hidden treasures may be found. Databases can be elaborate. Libraries often have created complex databases, called catalogs, which adhere to rigid standards and MARC format. The people who catalog this information have years of training and create sophisticated records that help library users. This also allows many English-speaking libraries to "pool" their resources and to share their catalogs online. The computers that drive these systems, and the software which organizes them, can frequently cost over $1 million. Unless you are associated with a very large city, state, university or the federal government, you may need to find a way to do something similar with much less money and staff. Choosing the database: The best way to do this is to use a good general database. Database software such as Microsoft Access or Claris Filemaker Pro can be purchased at computer stores or online and cost about $500. Filemaker will operate on both Mac and IBM-based systems, while Access currently works only on PC’s (IBM compatible Personal Computers). Unless you already have a Mac, it is probably better to use a PC at this time, as these dominate the market. Less expensive databases, particularly older ones, may be proprietary, meaning they are written in a special language not all software can read. Proprietary databases make the transfer of data to new versions or other software difficult or impossible. Exportability is one of the most important aspects in any database. This means that your data can be transferred to another database, either because you upgrade to a newer type or because you are linking (connecting) your information with other institutions, as many libraries do. The time is near when libraries, archives, museums and historical societies will all pool our information to help researchers find our resources. To ensure that your database is exportable and will work with others, look for the following:
The two databases we currently recommend are Claris FilemakerPro and Microsoft Access. Both meet all of the above requirements. Filemaker is easier to use, but Access represents the evolving future standard. Users of both can be certain that the sizes of the user network (the number of people who have that program) are large and important enough that they will be exportable in the future. Filemaker has the advantage of being Web- publishable, while both Filemaker and Access can be linked to digital files for Web display. Some other programs will automatically create or allow you to create HTML or SGML links, the code that allows the database to be used on the Web. Some of the specially designed programs for museums and archives have the same features and are easy to use. These tend to be more expensive, but if they are exportable and meet your needs, they may also be a good choice. Formatting the database: We recommend that you enroll in a workshop or consult with our Agency staff about the layout of your database. Every institution’s needs are different. The basic fields explained in Dublin Core are the most important for future connections, and they probably will also be the most common ones that you will use. But you may have other needs— circulation status, provenance (the history of the item in your collection), relationships within your collection (like a spittoon that was once used by an important person—you might not like spittoons, but this one belonged to Gov. Hunt, so you keep it). Once your computer hardware and database software are purchased it is important that you devote some time upfront becoming familiar with them. There is usually a tutorial. Going through the software carefully in the beginning will help you understand the boxes and layout that you might prefer, and find easy to work with. You can move fields around so that the ones important to you are where you see them first. When including ID numbers for digital files in a database, be sure to include the extension format on all PC computers. These should look something like .jpg or .tif. This will allow you to link them to HTML or other query languages. We have provided a sample template for Dublin Core records. Please use it if you wish, but also include elements and fields that are important to you. Give this considerable thought. It is much better to devote time laying out the database at the beginning, than it is to go back after you’ve created 5000 records and realize that you didn’t include the date of creation, or the physical description. Otherwise, after the fact, you might have to access each item’s record and add that information. Digitization GuidelinesThese are the recommended minimum guidelines for Arizona institutions involved in digitization projects in cooperation with the Arizona State Library, Archives and Public Records. Image files should be saved and scanned in at least three file sizes. Image files should not be cropped or altered, except for the removal of extraneous borders. Proper image calibration based upon grayscale measurements (not screen display) is presumed and is a critical component of the scanning process. These guidelines are for materials not to exceed 11" x 14".
Notes:
Scanning Hardware and Software Selection GuidelinesThe goals of your digitization project will determine what hardware and software are needed to successfully complete the project. Scanning, image manipulation, attaching text information, indexing, image display and long-term storage can require different equipment and user expertise. What materials are to be scanned and how those images are to be used will impact equipment choices. These selection guidelines are intended as general recommendations. Digitization is an area that is evolving and we strongly recommend that you research the current literature in print and online for the latest developments before purchasing any equipment. Consider the following before any equipment is purchased.
General specifications for hardware selection.
Scanners Flatbed scanners are recommended for most digitization projects. Flatbed scanners can be used for photographs, slides, and negatives in sizes up to 12x18. Scanners should be able to support reflected and transmitted light (for prints and transparencies or negatives) depending on current and projected future collection holdings. A transparency hood for the scanner is recommended if your project will include scanning of opaque and transparent media. Flatbed scanner (minimum resolution 600/1200 dpi with 32 bit depth) Repositories with significant numbers of 35mm slides and negatives may want to purchase a scanner dedicated to that format. Slide scanner(minimum resolution 2400 dpi with 32 bit depth) The digital camera promises to expand the digitization tool kit. Low resolution, relatively inexpensive digital cameras may be used to produce thumbnail images for publication on the World Wide Web. High-resolution digital cameras are costly devices that are not practical for use in most digitization projects. Special cases may require the use of a digital camera on copystand to permit digitizing flat art and 3-D objects and artifacts. The Records Management Division of this Agency offers vendor service to Arizona institutions for textual document imaging (not photographs). Contact Bill James for information. Other private vendors and institutions in Arizona and the Western U.S. also offer this service. General specifications for software selection Scanning software comes with the scanner itself. Image editing software (Adobe PhotoShop full version preferred over Adobe PhotoShop LE) is a necessity and must be purchased separately. General specifications for storage media selection CD-ReWritable is recommended for storage of data files, given the need for checking files before deletion of original copies, and development and implementation of a management strategy to regularly check the integrity of the files, and to migrate to new media as appropriate. Magnetic disk drives such as zip are an alternative to CD-RW for small capacity files. CD-RW for capacity up to 600MB Magnetic disk such as a Zip drive for capacity up to 100MB Accession/Accessioning: Accession
file: Accession
number: Accession
register: Acetone: Acid-free: Acquisition/Acquisitioning: Acryloid
B72: Active
stabilization: Appraisal: Archives: Archival
quality: Archivist: Assessment,
collections: Associated
records: Backing: Bequest: Buffer: Catalog: Cellulose
nitrate film Collection: Collecting
plan: Collecting
strategy: Collections
management: Collections
manager: Condition
report: Conservation: Conservator: Consolidant: Copyright: Corrosion: Courier: Crazing: Crizzling: Cultural
resources: Culling: Cultural
affiliation: Cultural
patrimony (objects of): Curation: Curation
agreement: Curator: Deaccession: Dead
storage: Deed
of Gift: Delamination: Derivative
work: Destructive
analysis: Devitrification: Disposal: Disposition: Disposition
schedule: Dry
cleaning: Ecofacts: Efflorescence: Environmental
Assessment (EA): Environmental
Impact Statement (EIS): Ethafoam®: Facility
report: Finding
aid: Flotation: Funerary
objects: Genre: Geographic
Information System (GIS): Gray
literature: Historic
preservation: Humectant: Humidification: Hygrothermograph: Information
Management: In
perpetuity: In
situ: Integrated
Pest Management: Intellectual
rights/ Intellectual property rights: Intervention/Interventive
materials: Inventory: Japanese
paper: Lineal
descendant: Loan: Loan
fee: Lossy compression:"...any process for compressing an image file that causes the file, once uncompressed to differ from the original appearance of the image file. Many lossy compression file formats look very similar to the uncompressed file, as the information that is discarded is often not easy to identify visually" (Vogt O'Connor 1999:49). Lot: Lux: Machine-readable
records: Material
remains: Memorandum
of Agreement (MOA): Metadata: Microform: Mission
Statement: Museum: Mylar®: National
Historic Landmarks Program: National
Register of Historic Places: Non-cultural
artifacts or materials: Original
order: Pest
management: pH
level /pH scale: Polyethylene
PE): Polymer: Polypropylene: Polyurethane: Polyvinyl
Acetate (PA) emulsion: Polyvinyl
Chloride (PVC): Processing,
initial: Project
design: Provenance: Provenience: Range
of variation: Records: "Federal records are defined as all books, papers, maps, photographs, machine readable materials, or other documentary materials, regardless of physical form or characteristics, made or received by an agency of the United States Government under Federal law or in connection with the transaction of public business and preserved or appropriate for preservation by that agency or its legitimate successor as evidence of the organization, functions, policies, decisions, procedures, operations, or other activities of the Government or because of the informational value of data in them." (36 CFR 1222.12). Records
management: Reemay®: Reformatting: Registrar: Rehabilitation: Relative
humidity (RH): Religious
use: Repatriation: Repository: Research
design: Risk
management: Sacred
objects: Sampling: Scope
of Collections: Security
copy: Series: Silica
gel: Soil
samples: Soluble
salt: Solvent: Spalling: State
Historic Preservation Officer (SHPO): Study
or type collection: Teflon
monofilament: Thermoplastic
acrylic: Thermosetting
resin: Type
collection: Ultraviolet
(UV) rays: Warping: Weeping: |
|