ࡱ> !y fbjbj  {{6/RRRRRT>T!9?BBBBC =OP$RRCCRRRRBBbbbR RBRBbRbbZ|B1CP`Hz 09 ba" ||\ RQ"QbQQQQQa|QQQ9RRRR QQQQQQQQQ : National Library of MedicineRecommendations on NLM Digital Repository Software  Prepared by the NLM Digital Repository Evaluation and Selection Working Group Submitted December 2, 2008 Contents  TOC \o "1-3" \h \z \u  HYPERLINK \l "_Toc225746170" 1. Executive Summary  PAGEREF _Toc225746170 \h 1  HYPERLINK \l "_Toc225746171" 2. Introduction and Working Guidelines  PAGEREF _Toc225746171 \h 2  HYPERLINK \l "_Toc225746172" 2.1. Introduction  PAGEREF _Toc225746172 \h 2  HYPERLINK \l "_Toc225746173" 2.2. Working Guidelines  PAGEREF _Toc225746173 \h 2  HYPERLINK \l "_Toc225746174" 3. Project Methodology and Initial Software Evaluation Results  PAGEREF _Toc225746174 \h 4  HYPERLINK \l "_Toc225746175" 3.1 Project Timeline  PAGEREF _Toc225746175 \h 4  HYPERLINK \l "_Toc225746176" 3.2. Project Start: Preliminary Repository List  PAGEREF _Toc225746176 \h 4  HYPERLINK \l "_Toc225746177" 3.3. Qualitative Evaluation of 10 Systems/Software  PAGEREF _Toc225746177 \h 4  HYPERLINK \l "_Toc225746178" 3.4. In-depth Testing of 3 Systems/Software  PAGEREF _Toc225746178 \h 7  HYPERLINK \l "_Toc225746179" 4. Final Software Evaluation Results  PAGEREF _Toc225746179 \h 9  HYPERLINK \l "_Toc225746180" 4.1 Summary of Hands-on Evaluation  PAGEREF _Toc225746180 \h 9  HYPERLINK \l "_Toc225746181" 5. Recommendations  PAGEREF _Toc225746181 \h 17  HYPERLINK \l "_Toc225746182" 5.1. Recommendation to use Fedora and Conduct a Phase 1 Pilot  PAGEREF _Toc225746182 \h 17  HYPERLINK \l "_Toc225746183" 5.2. Phase 1 Pilot Recommendations  PAGEREF _Toc225746183 \h 18  HYPERLINK \l "_Toc225746184" 5.3. Phase 1 Pilot Resources Needed  PAGEREF _Toc225746184 \h 19  HYPERLINK \l "_Toc225746185" 5.4. Pilot Collections  PAGEREF _Toc225746185 \h 21  HYPERLINK \l "_Toc225746186" Appendix A - Master Evaluation Criteria Used for Qualitative Evaluation of Initial 10 Systems  PAGEREF _Toc225746186 \h 23  HYPERLINK \l "_Toc225746187" Appendix B - Results of Qualitative Evaluation of Initial 10 Systems  PAGEREF _Toc225746187 \h 25  HYPERLINK \l "_Toc225746188" Appendix C DSpace Testing Results  PAGEREF _Toc225746188 \h 27  HYPERLINK \l "_Toc225746189" Appendix D DigiTool Testing Results  PAGEREF _Toc225746189 \h 41  HYPERLINK \l "_Toc225746190" Appendix E Fedora Testing Results  PAGEREF _Toc225746190 \h 53  1. Executive Summary The Digital Repository Evaluation and Selection Working Group recommends that NLM select Fedora as the core system for the NLM digital repository. Work should begin now on a pilot using four identified collections from NLM and the NIH Library. Most of these collections already have metadata and the NLM collections have associated files for loading into a repository. The Working Group evaluated many options for repository software, both open source and commercial systems, based on the functional requirements that had been delineated by the earlier Digital Repository Working Group. The initial list of 10 potential systems/software was eventually whittled down to 3 top possibilities: two open source systems, DSpace and Fedora, and DigiTool, an Ex Libris product. The Working Group then installed each of these systems on a test server for extensive hands on testing. Each system was assigned a numeric rating based on how well it met the previously defined NLM functional requirements. While none of the systems met all of NLM's requirements, Fedora (with the addition of a front end tool, Fez) scored the highest and has a strong technology roadmap that is aggressively advancing scalability, integration, interoperability, and semantic capabilities. The consensus opinion is that Fedora has an excellent underlying data model that gives NLM the flexibility to handle its near and long-term goals for acquisition and management of digital material. Fedora is a low-risk choice because it is open-source software, so there are no software license fees, and it will provide NLM a good opportunity to gain experience in working with open source software. It is already being used by leading institutions that have digital project goals similar to NLM's, and these institutions are an active development community who can provide NLM with valuable advice and assistance. Digital assets ingested into Fedora can be easily exported, if NLM were to decide to take a different direction in the future. Implementing an NLM digital repository will require a significant staffing investment for the Office of Computer and Communications Systems (OCCS) and Library Operations (LO). This effort should be considered a new NLM service, and staffing levels will need to be increased in some areas to support it. Fedora will require considerable customization. The pilot project will entail workflow development and selection of administrative and front end software tools which would be utilized with Fedora. The environment regarding repositories and long term digital preservation is still very volatile. All three systems investigated by NLM have new versions being released in the next 12 months. In particular, Ex Libris is developing a new commercial tool that holds some promise, but will not be fully available until late 2009. The Working Group believes NLM must go forward now in implementing a repository; the practical experience gained from the recent testing and a pilot implementation would continue to serve NLM with any later efforts. After the pilot is completed, NLM can re-evaluate both Fedora and the repository software landscape. 2. Introduction and Working Guidelines 2.1. Introduction In order to fulfill the Library's mandate to collect, preserve and make accessible the scholarly and professional literature in the biomedical sciences, irrespective of format, the Library has deemed it essential to develop a robust infrastructure to manage a large amount of material in a variety of digital formats. A number of Library Operations program areas are in need of such a digital repository to support their existing digital collections and to expand the ability to manage a growing amount of digitized and born-digital resources. In May 2007, the Associate Director for Library Operations approved the creation of the Digital Repository Evaluation and Selection Working Group (DRESWG) to evaluate commercial systems and open source software and select one (or combination of systems/software) for use as an NLM digital repository. The group commenced its work on June 12, 2007 and concluded its work December 2, 2008. Working Group members were: Diane Boehr (TSD/CAT), Brooke Dine (PSD/RWS), John Doyle (TSD/OC), Laurie Duquette (HMD/OC), Jenny Heiland (PSD/RWS), Felix Kong (PSD/PCM), Kathy Kwan (NCBI), Edward Luczak (OCCS), Jennifer Marill (TSD/OC), chair, Michael North (HMD/RBEM), Deborah Ozga (NIH Library) and John Rees (HMD/IA). Doron Shalvi (OCCS) joined the group in October 2007 to assist in the set up and testing of software. The group's work followed that of the Digital Repository Working Group, which created functional requirements and identified key policy issues for an NLM digital repository to aid in building NLM's collection in the digital environment. The methodology and results of the software testing are detailed in Sections 3-4 of this report. Section 5provides the Working Group's recommendations for software selection and first steps needed to begin building the NLM digital repository. 2.2. Working Guidelines 2.2.1. Goals and Scope of the NLM Digital Repository Institutional Resource The NLM digital repository will be a resource that will enable NLM's Library Operations to preserve and provide long-term access to digital objects in the Library's collections. Contents The NLM digital repository will contain a wide variety of digital objects, including manuscripts, pamphlets, monographs, images, movies, audio, and other items. The repository will include digitized representations of physical items, as well as born digital objects. NLM's PubMed Central will continue to manage and preserve the biomedical and life sciences journal literature. NIH's CIT will continue to manage and preserve HHS/NIH videocasts. Future Growth The NLM digital repository should provide a platform and flexible development environment that will enable NLM to explore and implement innovative digital projects and user services utilizing the Library's digital objects and collections. For example, NLM could consider utilizing the repository as a publishing platform,a scientific e-learning/e-research tool, or to selectively showcase NLM collections in a very rich online presentation. 2.2.2. Resources OCCS Staff will provide system architecture and software development resources to assist in the implementation and maintenance of the NLM digital repository. Library Operations Staff will define the repository requirements and capabilities, and manage the lifecycle of NLM digital content. 3. Project Methodology and Initial Software Evaluation Results 3.1 Project Timeline The Working Group held its kick-off meeting June 12, 2007 and completed all work by December 2, 2008. Phase 1: Completed September 25, 2007. A qualitative evaluation was conducted of 10 systems, and three were selected for in-depth testing. Phase 2: Completed October 22, 2007. A test plan was developed and a wide range of content types was selected to be used for testing. Phase 3: Completed October 13, 2008. Three systems were installed at NLM and hands-on testing and scoring of each was performed. On average,each system required 85 testingdays or just over four months from start of installation to completion of scoring. Phase 4: Completed December 2, 2008. The final report was completed and submitted. 3.2. Project Start: Preliminary Repository List Based on the work of the previous NLM Digital Repository Working Group, the team conducted initial investigations to construct a list of ten potential systems/software for qualitative evaluation. The group also identified various content and format types to be used during the in-depth testing phase. 3.3. Qualitative Evaluation of 10 Systems/Software The Working Group conducted a qualitative evaluation of the 10 systems, by rating each system using a set of Master Evaluation Criteria established by the Working Group (see Appendix A). Members reviewed Web sites anddocumentation, and talked to vendors and users to qualitatively rate each system. Each system was given a rating of 0 to 3 for each criterion, with 3 being the highest rating. Advantages and risks were also identified for each system. The Working Group was divided into four subgroups, and each subgroup evaluatedtwoorthree of the 10 systems. Each subgroup presented their research findings and initial ratings to the full Working Group. The basis for each rating was discussed, and an effort was made to ensure that the criteria were evaluated consistently across all 10 tools. The subgroups finalized their ratings to reflect input received from discussions with the full Working Group. All 10 systems were ranked, and three top contenders were identified(see Appendix B). DigiTool, DSpace, and Fedora were selected for further consideration and in-depth testing. Below are highlights of the evaluation of the 10 systems. ArchivalWare Developed by: PTFS (commercial). Advantages: Strong search capabilities. Risks: Small user population. Reliability and development path of vendor unknown. CONTENTdm Developed by: University of Washington and acquired by OCLC in 2006 (commercial). Advantages: Good scalability. Risks: No interaction with third party systems. Data stored in proprietary text-based database and does not accommodate Oracle. Development path of vendor unknown. DAITSS Developed by: Florida Center for Library Automation (FCLA) (open source)and released under the GNU GPL license as a digital repository system for 11 public universities. Advantages: Richest preservation functionality. Risks: Back-end/archive system. Must use DAITSS in conjunction with other repository or access system. Planned re-architecture over next 2 years. Limited use and support; further development dependent on FCLA (and FL state legislature). DigiTool Developed by: Ex Libris(commercial) as an enterprise solution for the management, preservation, and presentation of digital assets in libraries and academic environments. Advantages: "Out-of-the-box" solution with known vendor support. Provides good overall functionality. Has ability to integrate and interact with other NLM systems. Scalability and flexibility may be issues. Risks: NLM may be too dependent on one commercial vendor for its library systems. DSpace Developed by: MIT Libraries and HP Labs(open source) as one of the first open source platforms created for the storage, management, and distribution of collections in digital format. Advantages: "Out-of-the-box" open source solution. Provides some functionality across all functional requirements. Community is mature and supportive. Risks: Planned re-architecture over next year. Current version's native use of Dublin Core metadata is somewhat limiting. EPrints The Subgroup decided to discontinue the evaluationdue to EPrints (open source)lack of preservation capabilities and its ability to only provide a small-scale solution for access to pre-prints. Fedora Developed by: University of Virginia and Cornell University libraries (open source). Advantages: Great flexibility to handle complex objects and relationships. Fedora Commons received multi-million dollar award to support further development. Community is mature and supportive. Risks: Complicated system to configure according to NLM research and many users. Need additional software for fully functional repository. Greenstone Developed by: Cooperatively by the New Zealand Digital Library Project at the University of Waikato, UNESCO, and the Human Info NGO (open source). Advantages: Long history, with many users in the last 10 years. Strong documentation with commitment by original creators to develop and expand. Considered "easy" to implement a simple repository out of the box. DL Consulting available for more complex requirements. Compatible with most NLM requirements. Risks: Program is being entirely rewritten (C++ to Java) to create Greenstone 3. Delivery date unknown. Development community beyond the originators is not as rich as other open source systems. DL Consulting recently awarded grant "to further improve Greenstone's performance when scaled up to very large collections" -- implies it may not do so currently. Core developers and consultants in New Zealand. Keystone DLS Developed by: Index Data (open source). Advantages: Some strong functionality. Risks: Relatively small user population. Evaluators felt it should be strongly considered only if top 3 above are found inadequate. No longer actively being developed as of August 2008. VITAL Developed by: VTLS, Inc. (commercial) as a commercial digital repository productthat combines Fedora with additional open source and proprietary software and provides a quicker start-up than using Fedora alone. Advantages: Vendor support for Fedora add-ons. Risks: Vendor-added functionality may be in conflict with open-source nature of Fedora. 3.4. In-depth Testing of 3 Systems/Software DSpace, DigiTool, and Fedora were selected as the top three systemsto betested and evaluated. Four subgroups of the Working Group (Access, Metadata and Standards, Preservation and Workflows, Technical Infrastructure) were formed to evaluate specific aspects of each system. System testing preparation included: Creating a staggered testing schedule to accommodate all three systems. Selecting simple and complex objects from the NLM collection lists. Identifying additional toolsthat would be helpfulin testingDSpace and Fedora (e.g. Manakin and Fez). Developingtest scenarios and plans for all four subgroups based on the functional requirements. A Consolidated Digital Repository Test Plan was created based on the requirements enumerated in the HYPERLINK "http://www.nlm.nih.gov/digitalrepository/NLM Digital Repository Requirements rev March 2007.pdf"NLM Digital Repository Policies and Functional Requirements Specification.The Test Plan contains 129 specific tests, and is represented in a spreadsheet. Each test was allocated to one of the four subgroups, who were tasked to conduct that test on all three systems. DSpace 1.4.2, DigiTool 3.0, and Fedora 2.2/Fez 2 Release Candidate 1 were installed on NLM servers for extensive hands-on testing. OCCS conducted demonstrations and tutorials for DSpace and Fedora, and Ex Libris provided training on DigiTool, so that members could familiarize themselves with the functionalities of each system.The Consolidated Digital Repository Test Plan guided the testing and scoring of the three systems. Details of the testing are available in thenext section. 4. Final Software Evaluation Results The Technical Infrastructure, Access, Metadata and Standards, and Preservation and Workflows subgroups conducted the test plan elements allocated to their subgroup in the Consolidated Digital Repository Test Plan. Selecting from a capability/functionality scale of 0 to 3 (0=None, 1=Low, 2=Moderate, 3=High), the subgroups assigned scores to each element, indicating the extent to which the element was successfully demonstrated or documented. Scores were added up for eachsubgroup's setof test elements. A cumulative score for each system was calculated by totaling the four subgroup scores. The Fedora platform and Fez interface were evaluated as a joint system. 4.1 Summary of Hands-on Evaluation Subgroup DSpace DigiTool Fedora (w/Fez) Technical Infrastructure 36 51 49.75 Access 40 66 52.5 Metadata and Standards16 27.5 40.75 Preservation and Workflows42 45 56.5 Total Score 134 189.5 199.5 4.1.1. DSpace 1.4.2 Evaluation See Appendix C for complete testing results. 4.1.1.1. Technical Infrastructure, score=36 Data model well suited for academic faculty deposit of papers but does not easily accommodate other materials. All bitstreams uniquely identified via handles and stored with checksums. Very limited relationships between bitstreams (html document can designate the primary bitstream, hiding the secondary files that make up a web page). Workflow limited to three steps. Dublin Core metadata required for ingest. Other metadata can be accepted as a bitstream but would not be searchable. Versioning of objects/bitstreams not supported. Some usage and inventory reporting built-in. DSpace uses the database to store content organization and metadata, as well as administrative data (user accounts, authorization, workflow status, etc). 4.1.1.2. Access, score=40 User access controls are moderate, with authorizations logic restricting functions to admin users or authenticated users. Although objects can have text files associated as licenses, there is not application logic to make use of license data, and no built-in way to facilitate content embargoes/selective user access. Entire collections can be hidden to anonymous users, but metadata remains viewable. Audit history written to a cumulative log which must be parsed by scripts into human-readable formats, and metadata actions are only sparsely logged. External automated access to Dublin Core metadata via OAI-PMH. Content is searchable by Dublin Core metadata and full text. Files are listed in the order they were ingested and cannot be sorted. 4.1.1.3. Metadata and Standards, score=16 Dublin Core metadata required for ingest. Other metadata can be accepted as a bitstream but would not be searchable. Metadata validation not possible. Exporting of objects as METS files, but METS not currently supported as an ingest format. 4.1.1.4.Preservation and Workflows, score=42 Exported data can be re-ingested with a replace function. Checksum checker can periodically monitor the bitstreams for integrity. No normalization capability. No referential integrity checks. No tools for file migration. Provenance for record updates is lacking. 4.1.1.5. System support issues Platform support: DSpace runs on Solaris, Linux, other UNIX, or Windows servers. It is a Java application, anduses ApacheTomcat, Apache Ant, and other open source Java tools. DSpace uses a relational database that can be Oracle, PostgreSQL, or MySQL. Deployment and maintenance: OCCS personnel installed several copies of DSpace on Windows computers for initial testing and demonstration. OCCS then installed DSpace on an NLM Solaris server using an Oracle database for full testing and evaluation. DSpace is relatively simple to install and build, and has limited but adequate documentation.DSpace includes user interfaces for public access and repository administration; however, these interfaces are very plain, and difficult to customize. Installation and usage problems can often be solved by asking for assistance from members of the DSpace community,by posting a request on the DSpaceemail list server. Development and user organizations: DSpace has a very active user community and open source development community, with over 400 institutional users worldwide including NLM LHC for the SPER research project.DSpace was initially developed with support from MIT and HP. In 2007, the DSpace Foundation was formed to continue development of the open source software and support its community. Future roadmap: Future plans for DSpace are not crystal clear, but there is good promise for continued development and community support: ADSpace 2.0architecture has been defined that will introduce major improvements to the tool, anddevelopment of these enhancements has already begun. Plans are being made for significant collaboration with the Fedora Commons community, to address needs and functions that are common to these two tools. Grant funding for planning joint activities has recently been obtained from the Andrew W. Mellon Foundation. 4.1.1.6. User Visits/Calls University of Michigan (May 14, 2008) 4.1.2. DigiTool 3.0 Evaluation See Appendix D for complete testing results. 4.1.2.1. Technical Infrastructure, score=51 Overall, the group was impressed with the broad range of tools and continued to discover new functionality, although the discovery was difficult at times. The ingest process is one example of the difficulty the group experienced: understanding the use of the legacy Meditor and the web ingest tool and the difference between deposit and ingest. Ingest workflows seemed overly complex. Certain challenges were a result of the NLM environment: the security lockdown, the Meditor installation, and ActiveX. Quite a few tests were conducted. The group was particularly happy with the range of file types (DigiTool really shines in this area) and areas of metadata handling, especially in terms of METS. Other positive aspects are the automatic format configurations and the support of relationships between digital entities (parent-child, for example). Weak areas include lack of specific support for quality assurance and audit functionality and the overall system configuration management. Standards support is good. 4.1.2.2. Access, score=66 The group's evaluation considered staff users as well as end user needs and functionality. Access features in both areas were pretty strong, in terms of granularity of permissions, access protocols (Z39.50, OAI-PMH, etc.), and the search results display. The group would like to see more flexibility in search options, such as relevance ranking, proximity, and "more like this." Poor browsing features and no leveraging of authority control. The group recognizes many of these features are available via Primo and through some customization of Oracle. Good faith effort towards Section 508 compliance is well-documented by the vendor. Generally, the feeling is that DigiTool very strong in the access area. 4.1.2.3. Metadata and Standards, score=27.5 Ingest of multiple format types is a feature the group likes. The limitation to Dublin Core mapping is a hindrance. The group would like to see more information on validation (for example, validation that a MeSH heading is MeSH). Updating and adding metadata fields are easy. The group did not see metadata checking for batch files, only individual files. 4.1.2.4.Preservation and Workflows, score=45 DigiTool has many rich features, especially the use of METS extraction, JPEG 2000 thumbnail creation, and tagging master files in two ways. The rollback feature is good. Weak areas include the lack of confirmation for ingest and individual rather than batch ingest. The group recognizes that most preservation functionality will be offered with the Ex Libris Digital Preservation System (DPS), currently in development. Many customers will continue using DigiTool and have no need for the enhanced preservation functionality that will be offered by the DPS. 4.1.2.5.System support issues Platform support: DigiTool runs on either a Solaris or Linux server, with an embedded Oracle database. The Meditor administrative client software runs on a desktop PC. Deployment and maintenance: Installation was performed by Ex Libris on an NLM Solaris server; the vendor willnot allow the software to be installed by the user organization. The installation requirements presented no particular difficulties, with the exception of the Meditor client software which required administrator privilege to install on user PCs. Parts of the code base are very old, having been migrated from a legacy COBOL product. Ex Libris provided detailed training on the use of the software, and was responsive in answering questions. Development and user organizations: The DigiTool product development team is located in Israel, and is accessible via web conference and teleconference. A separate team at Ex Libris is also developing a new repository product, the Digital Preservation System. Contacted users reported mixed experiences with DigiTool - a few are happy (e.g., Boston College), but others were disappointed and abandoned the product (e.g., University of Maryland, University of Tennessee, and Brandeis University). A small but active user group exists. Future road map: Ex Libris recently indicated to NLM that DigiTool will cease to be an independent product, and will be reformulated as a module that can be optionally used with the new Ex Libris Digital Preservation System.These plans have not yet been publicly announced. Security: OCCS conducted a web application security scan of DigiTool using IBM's AppScan scanning tool, and found 126 high-severity issues and 22 medium-severity issues. The high-security issues included Cross-Site Scripting vulnerabilities and Blind SQL Injection vulnerabilities. An additional 229 low-severity issues and information issues were detected by the scan. Details are provided in the DRESWG Security Scan Results. 4.1.2.6. User Visits/Calls Boston College (May 2, 2008) Oak Ridge National Library (May 7, 2008) University of Tennessee, Knoxville (email exchange on DigiTool 3 beta testing in 2005; May 28, 2008) Center for Jewish History and The Jewish Theological Seminary (May 30, 2008) 4.1.3. Fedora 2.2/Fez 2 Release Candidate 1 Evaluation See Appendix E for complete testing results. 4.1.3.1. Technical Infrastructure, score=Fedora: 40.5; Fez: 35.5; Combined Fedora/Fez maximum: 49.75 Fedora is very strong in the range of files that can be ingested, metadata requirements, versioning, relationships, and audit trails. Fedora's web services-based interface to repository content makes it easy to integrate with external tools and custom front-ends. Fedora is weak in workflow capabilities. Fez ranges from minimum to adequate in workflow capabilities. Fedora provides good support for standards compliance: SOAP, OAI, Unicode, METS, PREMIS, etc. One question is whether Fedora can catch transmission errors when a file is ingested from a directory, a function available in SPER. Fedora can compute a checksum and add it to the SIP, and it will verify checksums, but there appears to be a bug: the checksums always match. This problem should be fixed in version 3.0. 4.1.3.2. Access, score=Combined Fedora/Fez: 52.5 Fedora provides great flexibility and granularity re: access controls at the user, collection, object, datastream and disseminator levels. The downside to this flexibility is that it requires custom policies to be written using a specialized markup - learning curve for the admin/developer staff. Fez also has granular security options, including Active Directory integration. The Group was not able to successfully test some of the access control logic. A big downside to the administration of the controls is the need to multi-select values using the Ctrl key, making it very easy to accidently deselect values which may not even be visible to the user. Fedora includes an OAI-PMH service which can provide the Dublin Core metadata associated with an object. This service could run (on Fedora) with a Fez implementation as well. Fedora has a very basic default end-user interface but is extremely flexible in its ability to integrate with third-party front-ends. Fez offers a rich end-user UI including UTF8 character support, controlled keyword searching, and output into RSS. Both systems do not adequately highlight a preferred version of an object over other versions also made visible to the end user. Full text searching is available with both systems via a third-party indexing plug-in. Fedora's disseminator approach offers much flexibility to content delivery, and Fez's inability to leverage the dissemination is a significant downside to the Fez product. 4.1.3.3. Metadata and Standards, score=Fedora 40.75; Fez 33.75; Combined Fedora/Fez: 40.75 Most of the ratings assigned were 3s. The most difficult aspect of Fedora is determining workflows. Fedora conducts all the metadata checks that are needed. Fedora is difficult to use, as is DigiTool; Fez is easier. Fez uses only schemas, not DTDs. Dublin Core, MODS, and so on can be used as long as they are built into the workflow. MARC is ingested as a datastream. Disseminator architecture and other Fedora data model features should enable NLM to implement metadata linkage or exchange between Fedoraand Voyager. 4.1.3.4.Preservation and Workflows, score=Fedora: 55; Fez: 41.5; Combined Fedora/Fez maximum: 56.5 Fedora provides a solid core set of preservation capabilities that can be extended with companion tools (e.g. JHOVE for technical metadata extraction). Fedora/Fez does not create a physical AIP package but generates a FOXML/METS file that contains metadata and links to all datastreams during ingest. Fedoraassigns a PID and generates achecksum for each ingested datastream. Fez can generate three different.jpg derivatives for each ingested image datastream. The subgroup was unable to test Fedora's disseminator. GSearch (the Fedora Generic Search Service) may be implemented with Fedora toindex all metadata captured in FOXML/METS but style sheets must be written to enable GSearch functionality. Fedora allows data to be exported in three different ways: archive, migrate and public access but Fez has a very limited data export function. Fedora/Fezprovidesingest confirmationon screen but no summary statistics. The subgroup was unable to test mail notification functionality because the mail server was not set up. The purge function in Fez does not delete an object from the repository. In Fedora, purging deletes an object. Still have a need for workflows, if not for the software itself than for external business functions. 4.1.3.5. System support issues User interface: Fedora does not include a public web access user interface, so anexternalinterface must beadded. Options include open source tools designed for use with Fedora such as Fez andMuradora, or customweb pages developed in-house. The Fez product restricts Fedora's flexibility in some key areas (access controls and content modeling) and appears to be more tightly integrated into Fedora than other front ends (which could be swapped out without touching the content or core services). New versions of the Fez and Muradora tools are expected to be released in the next few months, and the Fedora Commons organization is now focusing attention on the Fedora community's need for a flexible user interface approach. Search: Fedora includes an optionalsearch component called GSearch that can search any metadata or text data in the repository. Because of time limitations, only the more limited default Fedora search component wastested. The full GSearch componentshould be implemented with Fedora. Resource Index database for storing relationships among objects as semantic concepts for querying by discovery tools. Platform support:Fedora runs on Solaris, Linux, other Unix, or Windows servers. It is a Java application, and uses Apache Tomcat, Apache Ant, and other open source Java tools. Fedora uses a relational database that can be Oracle, MySQL, PostgreSQL, McKoi, or others. Deployment and maintenance: OCCS personnel installed several copies of Fedora on Windows computers for initial testing and demonstration. OCCS then installed Fedora on an NLM Solaris server using an Oracle database for full testing and evaluation. Fedora is easy to install and is accompanied by clear and comprehensive documentation. An installation script is provided that guides the installation and configuration process. Fedora 2.2.2 was the production release version of the software when the NLM evaluation began, and was the version installed for testing. During testing, Fedora 3.0 was released, a significant upgrade with new features and simplified code base. NLM spoke with several Fedora users, and all plan to upgrade to version 3.0. Fedora 3.0 should be used instead of earlier versions. Development and user organizations: Fedora has an active user community, with more than 100 user institutions listed in the Fedora Commons Community Registry. The first prototype of Fedora was begun in 1997, and the project was led for several years by University of Virginia and Cornell University with grant money obtained from the Andrew W. Mellon Foundation. In 2007, Fedora Commons was incorporated as a non-profit organization, and received nearly $5 million in grant money from the Gordon and Betty Moore Foundation to continue development of the Fedora software, and to provide the resources needed to build a strong open source community. Fedora Commons supports the user and developer community with an active project web site, a wiki, and several email lists. All source code is managed on SourceForge. The Moore grant funds a leadership team, chief architect,lead developer, and several software developers. Several dozen additional developers are actively involved in the community at user institutions. Fedora is being used by leading institutions that have digital projects goals similar to NLM's.The users NLM has contacted are enthusiastic and confident in their choice of Fedora. They are building effective digital collections, and they can provide valuable advice and lessons-learned to NLM. Fedora is built using technologies that OCCS is prepared to support, includingJava, Tomcat, XML, and web services. Future roadmap: The Fedora Commons Technology Roadmap is published on the Fedora Commons web site, and defines the Fedora vision, goals, priorities, and five major projects, with detailed development plans and schedules. Some projects are primarily directed by Fedora Commons, and others are collaborations with other open source projects. Security: OCCS conducted a web application security scan of Fedora using IBM's AppScan scanning tool, and found 1 high-severity and1low-severity issues. The high-security issue was a Cross-site scripting vulnerability.The remediation for this vulnerability is to filter out hazardous characters from user input. This issue should be addressed in consultation with the Fedora Commons community leadership. The AppScan tool provides detailed information about the vulnerability and the coding approach needed to correct it. Additional details of the security scan are provided in the DRESWG Security Scan Results. 4.1.3.6. User Visits/Calls University of Maryland (August 7, 2007 Site Visit) University of Virginia (Sept 11, 2008) Indiana University (Sept 16, 2008) Tufts University (Sept 17, 2008) Rutgers University (Sept 18, 2008) Presentation from Thornton Staples of Fedora Commons (Sept 29, 2008) Yale University (Oct 3, 2008) 5. Recommendations 5.1. Recommendation to use Fedora and Conduct a Phase 1 Pilot The Digital Repository Evaluation and Selection Working Group recommends Fedora as the core system for the NLM digital repository and to start now on a phase 1 pilot to involve real collections. Fedora's architecture should enable NLM to ingest, manage, and deliver exotic content as well as the typical digital scans of print originals. It has the potential to encourage creative approaches to digital library research and development, e-publishing, e-scholarship, and e-science. Fedora has been implemented by a number of institutions involved in innovative digital services, including Indiana University, Rutgers University, Tufts University, the University of Virginia, the Max Planck Society (eSciDoc), the National Science Foundation (The National Science Digital Library), the Public Library of Science, and the Inter-University Consortium for Political and Social Research. Drawbacks include the extensive customization, training, and support required to implement and manage the complex architecture. Considerable time also will be invested in developing detailed workflows for Fedora. These risks, while significant, do not outweigh the system's benefits. 5.1.1 Key reasons for Fedora Provides the flexibility that will be needed to handle NLM's near-term and foreseeable future needs. Has a strong technology roadmap that is aggressively advancing scalability, integration, interoperability, and semantic capabilities. Is being used by leading institutions that have digital projects goals similar to NLM's. Has an active open source development community that is well-funded with grant money. Fedora is cutting edge yet bounded by a strong commitment to standards. Strongest and most flexible metadata support of all candidates - it is not bound to any single scheme. Hands-on functional testing has demonstrated that Fedora by itself scored well against NLM functional requirements, and, with the Fez add-on front-end tool, scored higher than DSpace and DigiTool. Fedora is a low-risk choice for NLM at this time: Fedora is open source software, so there are no software license fees. Other institutions like NLM are building effective digital collections using Fedora, and they can provide valuable advice and lessons-learned. Digital assets ingested into Fedora can be easily exported, if NLM were to decide to take a different direction in the future. Fedora is a good opportunity for NLM to gain experience with open source software. Fedora is developed and maintained using technologies that OCCS can support. 5.1.2. Future Actions Needed After the completion of a pilot, NLM should evaluate its work. Evaluation is a prudent plan to mitigate any risks associated with using Fedora. The pilot group should also re-evaluate the repository software landscape as new versions of all the tools examined are coming out over the next 12 months, including: Fedora just released version 3.1 which makes significant improvements in defining the content model. DSpace architecture will undergo major improvements with a new version, DSpace 2.0. Plans are also being made for significant collaboration between the DSpace and Fedora communities and NLM should keep abreast of how these plans could support NLM's use of Fedora. The pilot group may also want to determine if NLM should conduct a formal test of the Ex Libris Digital Preservation System (DPS). DPS is an emerging new commercial tool that offers future promise for digital repository applications: DPS is being developed to meet the requirements of the National Library of New Zealand (NLNZ), which rejected DigiTool. Release 1.0 is expected to be generally available by end of 2008/early 2009. NLNZ has gone live with DPS and is happy with the results so far. 5.2. Phase 1 Pilot Recommendations NLM should start with Fedora 3.1, the latest production release version. NLM hasn't exhaustively tested 3.x but is starting to examine the code and new key features. Other institutions which the group has spoken with are planning to migrate from 2.x to 3.x. 5.2.1. Companion Tools Use of Fedora open source software gives NLM the opportunity to select and incorporate "best-of-breed" companion tools. NLM can replace or add new tools as better alternatives become available. Tool awareness, evaluation, and selection will be a part ofNLM's repository evolution process. Companion tool investigation needed during phase 1 pilot: Administrative interface tools: The pilot group should not commit immediately to Fez but should investigate alternative administrative interface tools such as Muradora or the Rutgers Workflow Management System. Preservation tools: Determine use of JHOVE and related tools such as DROID for file identification, verification and characterization. Public user interface tools: Research and implement either open source or commercial page turning or other front end access capabilities and software. 5.2.2. Workflows The pilot group should make workflow recommendations over time and workflows may be tied to the collection or type of material. Workflows to be initially examined probably include metadata needed for SIPs (Submission Information Package) and format characterization. 5.2.3. Suggested Phase 1 Pilot Scope and Time Frame 6-8 months: Develop a first pilot collection that already has metadata and associated files. Produce a "quick" success to show progress. Manage the content in one secure place. Focus on defining the core functions in the areas of: data models, metadata, preservation and SIP creation. Investigate interfaces with Voyager to maximize use of existing metadata. Provide an initial public presentation using a simple Web interface. Investigate and begin to implement key preservation aspects to ensure master files are preserved. 8-18 months: Implement an additional one or two pilot collections (of the 4 proposed in section 5.4). Begin making recommendations on institutional workflows. Implement an administrative interface or collaborate with other users to evolve some open source alternative, or integrate/develop our own. Implement one or two unique public access capabilities (e.g., a page turning application). 5.2.4. NLM's Role in the Fedora Open Source Community NLM should investigate potential participation in the Fedora Commons community, e.g., the Fedora Preservation and Archiving Solution Community group. Participation could enable NLM to influence future software features. NLM should also investigate potential partnerships with leading Fedora users, e.g., University of Maryland, University of Virginia, or others. (These are strategic/managementdecisions.) NLM should consider contributing source code to the Fedora community only after the pilot phase, if NLM decides to continue its use of Fedora. NLM should become a participant rather than a "lurker." Before NLM shares any code it may want to consult with NIH legal counsel. 5.3. Phase 1 Pilot Resources Needed The following summarized resources are estimated for the phase 1 pilot. Additional resource needs may be identified during the pilot and may be dependent on the collection(s) to be implemented. 5.3.1. LO .8 FTE Project Manager and Analyst. Develops phase 1 pilot plan including scope, schedule and deliverables. Tracks changes to requirements and monitors project progress. Provides technical input and oversight of all major functional areas. .5 FTE Metadata Specialist 2.1 FTE Analyst All the above to perform the following: Analyze and develop workflows for various ingest and process models. (Refers to both single-file and batch mode). Determine metadata schema(s) and element requirements for technical and descriptive metadata. Define user community and access permissions. Develop specifications, specify requirements for interfaces with other internal systems and assist in developing integration plans for identified tools. Develop specifications for management, preservation, and statistical reports including access methods, file formats, and delivery options. Define data requirements including file formats, directory structure and information package for ingest. Develop QA checklists for automatic and manual processes including data integrity checks and file format identification, validation and characterization. Specify automatically generated error/confirmation/summary reports. (Refers to master, derivative and metadata files). Define derivative requirements. Develop preservation plan including master file management, integrity checks, backup plan, file migration, etc. .5 FTE User Interface Analyst. Takes lead in designing staff and public web interfaces, including search options and viewing capabilities. Insures that usability testing, performance analysis, and 508 compliance are conducted according to NLM guidelines and standards. Additional guidelines may need to be developed depending on user needs for repository collections and formats. 5.3.2. OCCS 1 FTE Systems Architect/Analyst/Engineering Project Manager. Responsible for working with LO on implementation specifications, advising on technical options, tracking development progress, providing status updates, coordinating implementation efforts among different OCCS groups, building development team, etc. Performs analysis of open source and commercial software tools, including discussions with users, community members, and vendors. 1 FTE Software Engineer/Programmer. Responsible for installing, developing and testing programs and scripts. Provides overview and demonstrates new tools. Implements and tests integration of new and existing tools. .3 FTE Web Developer/User Interface Specialist. Primary responsibility for public interface design and programming. Works with User Interface Analyst on designing usable administrative/staff interfaces. Systems Engineer responsible for server preparation, network setup, system software configuration, etc. Database Administrator responsible for database configuration and administration. 5.4. Pilot Collections The Working Group recommends the following digital collections as pilots for the repository in order to gain early implementation experience with many of the key capabilities of the selected NLM digital repository software. The files and metadata needed for the proposed collections are already available or can be compiled without significant effort. The Working Group recommends a variety of collection and file types be selected. 5.4.1. Cholera Monographs HMD/RBEM and PSD/PCMhave already scanned over 400 English language monographsin the collection relating to cholera dating from 1830 to 1890. HMD has already loaded many of the files online on a web site called HYPERLINK "http://www.nlm.nih.gov/exhibition/cholera/"Cholera Online, but the site is not searchable, except as part of the general NLM web search. Many of the PDFs are too large to download easily without a high speed connection.LO has high resolution tiff files with high quality technical metadata and METS/ALTO packages, of which the NLM digital repository should be able to use.Descriptive metadata for the materials already exists in Voyager. The Working Group would like to see a page turner installed for easy viewing of the materials in an online book-like format. 5.4.2. Digitized Motion Pictures HMD has digitized a number of its historical audiovisuals for preservation and access purposes, and those created by the government are in the public domain. Metadata for these historical films already exists in Voyager. The Working Group proposes that as a pilot project, LO attempt to load about ten of these historical audiovisuals into the NLM digital repository. NLM may need to gain a waiver to post material in the NLM digital repository that are not 508 compliant; in the case of digitized motion pictures, this would require expensive closed captioning of any films put into the NLM digital repository. 5.4.3. Image Files from Historical Anatomies on the Web HMD has selected and digitized over 500 images from important historical anatomical atlases in the collection and put them onto the web site, HYPERLINK "http://www.nlm.nih.gov/exhibition/historicalanatomies/home.html"Historical Anatomies on the Web.The images are not searchable, however, by subject, artist, or author. Metadata does not exist for these individual images, so the Working Group proposes to add about 50 of the images from two of the most famous atlases (HYPERLINK "http://www.nlm.nih.gov/exhibition/historicalanatomies/vesalius_home.html"Vesalius' _De Fabrica_and HYPERLINK "http://www.nlm.nih.gov/exhibition/historicalanatomies/albinus_home.html"Albinus' _Tabulae sceletai_) in order to allow thepilot team to learn how to handle image files and enter metadata into the system. 5.4.4. NIH Institute Annual Reports (jointly with NIH Library) Each year NIH Institutes and Centers issue annual reports, documents that provide historical perspective on research activities. Annual reports consist of a list of investigators for each research project and a project summary. More detail may be provided through individual project reports, which describe research objectives, methods, major findings, and resultant publications. In the mid-1990s, digital copies of many of the reports began to appear on Institute and Center web sites. Since 1998, intramural reports also have been submitted to the NIH Intramural Database for searching and viewing by NIH staff and the public (see NIDB Resources at HYPERLINK "http://intramural.nih.gov/mainpage.html"http://intramural.nih.gov/mainpage.html). The NIH Library maintains a collection of older print NIH annual reports, totaling more than 700 volumes. To fill gaps in digital access, the Library plans to digitize the annual report collection, beginning with reports issued by the Clinical Center. The Clinical Center annual reports span thirty-five years, from 1958 to 1993. A pilot collection of eleven volumes has been selected for digitization and deposit in the NLM digital repository, covering fiscal years 1981 through 1993. Appendix A - Master Evaluation Criteria Used for Qualitative Evaluation of Initial 10 Systems NLM Digital Repository Master Evaluation Criteria Updated August 13, 2007 Purpose Provide a decision method to select 3-4 systems for installation and testing at NLM from the initial list of 10 digital repository candidate systems. Context The Digital Repository Evaluation and Selection Working Group (DRESWG) has begun evaluating the initial list of 10 candidate systems against a list of approximately 175 functional requirements specified in the NLM Digital Repository Policies and Functional Requirements Specification, March 16, 2007. A weighted numerical scoring method is being used to compute a total score for each candidate system. The Functional Requirements score is one of the master evaluation criteria. Additional master evaluation criteria address other programmatic factors and risks that should be considered in the down-selection decision. Master Evaluation Criteria Functionality - Degree of satisfaction of the requirements enumerated in the NLM Digital Repository Functional Requirements Specification OR Evaluation: Numeric score as assessed by the Working Group Scalability Ability for the repository to scale to manage large collections of digital objects. Evaluation: 0-3 assessment scale (see below) Extensibility Ability to integrate external tools with the repository to extend the functionality of the repository, via provided software interfaces (APIs), or by modifying the code-base (open source software). Evaluation: 0-3 assessment scale (see below) Interoperability Ability for the repository to interoperate with other repositories (both within NLM and outside NLM) and with the NLM ILS. Evaluation: 0-3 assessment scale (see below) Ease of deployment Simplicity of hardware and software platform requirements; simplicity of installation; ease of integration with other needed software. Evaluation: 0-3 assessment scale (see below) System security How well does the system meet HHS/NIH/NLM security requirements? Evaluation: 0-3 assessment scale (see below) System performance How well the system performs overall; response time (accomplished via load testing). System availability (24x7 both internally and externally?). Evaluation: 0-3 assessment scale (see below) Physical environment Ability for multiple instances for offsite recovery; ability to function with the NIH off-site backup facility (NCCS); ability for components to reside at different physical locations; ability for development, testing and production environments; capability for disaster recovery. Evaluation: 0-3 assessment scale (see below) Platform support Operating system and database requirements. Are these already supported by OCCS? Is there staff expertise to deal with required infrastructure? Preferable: O/S: Solaris 10 (container); Storage: On NetApp via NFS; DB: Oracle; Web: java-tomcat or other application tier technology (OCCS will evaluate) Acceptable: O/S: Windows 2003, Linux Red Hat ES; DB: MySQL; Web: (no constraints for now OCCS will evaluate) Evaluation: 0-3 assessment scale (see below) Demonstrated successful deployments Relative number of satisfied users (organizations). Evaluation: 0-3 assessment scale (see below) System support Quality of documentation, and responsiveness of support staff or developer/user community (open source) to assist with problems. Evaluation: 0-3 assessment scale (see below) Strength of development community Reliability and support track record of the company providing the software; or size, productivity, and cohesion of the open source developer community. Evaluation: 0-3 assessment scale (see below) Stability of development organization Viability of the company providing the software; or stability of the funding sources and organizations developing open source software. Evaluation: 0-3 assessment scale (see below) Strength of technology roadmap for the future Technology roadmap that defines a system evolution path incorporating innovations and next practices that are likely to deliver value. Evaluation: 0-3 assessment scale (see below) To be considered only after the functional and technical criteria above are addressed: Cost Expected total cost of software deployment, including initial cost of software, plus cost of software integration, modifications, and enhancements. Evaluation: 0-highest cost 3-lowest cost Assessment Scale 0 None 1 Low 2 Moderate 3 High Appendix B - Results of Qualitative Evaluation of Initial 10 Systems Final Systems Evaluation Matrix Last updated: September 25, 2007  SEQ CHAPTER \h \r 1Type (open source, vendor)AdvantagesRisksFor further investigationNotesTop contendersFedoraOpen sourceGreat flexibility to handle complex objects and relationships. Fedora Commons received multi-million dollar award to support further development. Community is mature and supportive.Complicated system to configure according to our research and many users. Need additional software for fully functional repository.DigiTool (Ex Libris)VendorOut-of-the-box solution with known vendor support. Provides good overall functionality. Has ability to integrate and interact with other NLM systems.Scalability and flexibility may be issues. NLM may be too dependent on one vendor for its library systems.Ingest issuesDSpaceOpen sourceOut-of-the-box open source solution. Provides some functionality across all functional requirements (7.1-7.6) Community is mature and supportive.Planned re-architecture over next year. Current versions native use of Dublin Core metadata somewhat limiting.Further evaluation and discussion neededDAITSSOpen sourceRichest preservation functionalityBack-end/archive system. Must use DAITSS in conjunction with other repository or access system. Planned re-architecture over next 2 years. Limited use and support; further development dependent on FCLA (and FL state legislature).If selected for testing, code base needs examination for robustness. GreenstoneOpen sourceLong history, with many users in the last 10 years. Strong documentation with commitment by original creators to develop and expand. Considered easy to implement (library school students have used it to create projects) a simple repository out of the box; DL Consulting available for more complex requirements. Compatible with most NLM requirements.Program is being entirely rewritten (C++ to Java) to create Greenstone 3. Delivery date unknown. Development community beyond the originators is not as rich as other open-source systems. DL Consulting recently awarded grant to further improve Greenstones performance when scaled up to very large collectionsimplies it may not do so currently. Core developers and consultants in New Zealand.If selected for testing, not entirely clear whether Greenstone 3 (in beta) or Greenstone 2 (robust but going away) would be best to test with. Developers claim any system implemented in Greenstone 2 will be compatible with Greenstone 3. Should probably contact Greenstone developers and/or DL Consulting with this question if we select it.Keystone DLSOpen sourceSome strong functionality.Relatively small user population. Evaluators felt it should be strongly considered only if top 3 above are found inadequate.No further consideration needed at this timeArchivalWare (PTFS)VendorStrong search capabilities.Small user population. Reliability and development path of vendor unknown.Very low rating across all master criteria.CONTENTdm (OCLC)VendorGood scalability.No interaction with third party systems. Data stored in proprietary text-based database and does not accommodate Oracle. Development path of vendor unknown. Lower ratings across majority of master criteria.EPrintsOpen sourceLower ratings across majority of master criteria.VITAL (VTLS)VendorVendor support for Fedora add-onsVendor-added functionality may be in conflict with open-source nature of Fedora.If full evaluation of Fedora is successful, VITAL may be considered as an add-on. Appendix C DSpace Testing Results Consolidated Digital Repository Test Plan Last updated: March 4, 2008Source Require-mentsSub- group See Note 1 DSpace 1.4.2 TestsTest IDTest Plan ElementTest Procedure and ResultsScore (0-3) Note 2Notes7.1.1 Ingest - Receive SubmissionT7.1.1.7File types - Demonstrate that the system can ingest content in all the file formats listed as "supported" in Appendix B of the NLM DR Functional Requirements document (plus MP3 and JPEG2000), specifically: MARC, PDF, Postscript, AIFF, MPEG audio, WAV, MP3, GIF, JPEG, JPEG2000, PNG, TIFF, HTML, text, RTF, XML, MPEG. Demonstrate that the system can ingest the following types of content: articles, journals, images, monographs, audio files, video files, websites, numeric data, text files, and databases. Conduct this test element by ingesting the set of files listed in the Test File spreadsheet. (The files listed in this spreadsheet contain examples of all the file formats, and all the content types identified above.)7.1.1.7 7.1.1.9TAll files can be ingested. It is an implementation decision as to how the files/content are structured. Testing of "primary bit stream" for HTML files (KK): Shows primary bit stream file but hides all other files regardless of how related to HTML doc. Does not change original links in HTML doc.37.1.1.1Manual review - Demonstrate that the system has the capability to require that submitted content be manually reviewed before it is accepted into the repository. Demonstrate that the system maintains submitted content in a staging area before it is accepted. Demonstrate that the system notifies a reviewer when new content is ready for review. (Also see tests for 7.1.4.1, 7.1.4.2, and 8.1.2.)7.1.1.1TWorkflow limited to 3 steps, although this will be generalized in next release, 1.5.37.1.1.2Review and acceptance workflow - Demonstrate that the system supports a workflow for the review and acceptance of submitted content. Demonstrate that the workflow includes the following functions: - Receive and track content from producers; YES - Validate content based on submitter, expected format, file quality, duplication, and completeness; NO - Normalize content by converting content into a supported format for final ingestion into the repository; NO - Human review of content; YES - Acceptance or rejection of content or file format. YES 7.1.1.2, 7.1.1.10TJHOVE or similar needed for file validation. Tools/scripts available to parse log files.27.1.1.3Reason for rejection - Demonstrate that the system records a set of identifying information or metadata that describes the reason for the rejection of submitted content. Demonstrate two cases: (1) automatic rejection, and (2) rejection by a human reviewer.7.1.1.3TDSpace doesn't record the reason for rejection anywhere. The text of the reason that is manually entered by a reviewer is sent in an email back to the submitter, but the reason is not recorded in the DSpace database or the log file. The rejected item is kept as an "Unfinished Submission" in the submitter's My DSpace area, but the reason for rejection is not included with the item.07.1.1.4Rejection filter - Demonstrate that the system allows the creation of a filter that can be used to automatically reject submitted content. (This capability will eliminate the need for manual review of some submissions and resubmissions.)7.1.1.4T07.1.1.5Rejection notification - Demonstrate that the system can notify the producer or donor when submitted content is rejected. Demonstrate two cases: (1) notification after immediate rejection by an automated process, and (2) notification after rejection by manual review.7.1.1.5, 7.1.1.11T1 - No 2 - Yes by email1(7.1.1.8)Metadata types - Demonstrate that the system can ingest content with associated metadata in the following formats: all NLM DTDs, Dublin Core, MARC21, MARCXML, ONIX, MODS, EAD, TEI, PREMIS, METS. (NOTE: This test is covered by tests 8.1.1, 8.1.8, and 8.1.9)7.1.1.8, 8.1.1, 8.1.8, 8.1.9M/TDublin Core only1 (M & T)7.1.1.10Format conversion - Demonstrate that the system has the capability to convert the format of a file being ingested to a desired supported format. As a test case, demonstrate that a WAV file can be converted to MP3 format when it is ingested. (An external tool may be needed to perform the conversion. If this is the case, demonstrate that the system can invoke the required external tool.) 7.1.1.10, 7.1.1.2TDefinitely not a showstopper. External tool could possibly be used.07.1.1.12Resubmission - Demonstrate that the system can ingest a SIP that is resubmitted after an error in the SIP was detected and corrected. Demonstrate two cases: the resubmission can occur after an error was detected in (1) the content of the SIP, and (2) the metadata of the SIP.7.1.1.12TIf an item is rejected by a reviewer, an email containing the reason for rejection is sent to the submitter. The rejected item is kept in the submitter's My DSpace area as an "Unfinished Submission." The submitter can edit the item, correct any errors, and resubmit it. When format errors are detected during batch submission, the error is reported in the command window where the batch submission command is run. The administrator can manually correct the format errors, and resubmit the item in another batch submission. There is no duplication checking.27.1.1.14Versions - Demonstrate that the system can store, track, and link multiple versions of a file.7.1.1.14TPlanned for version 1.6 or 2.007.1.1.15aUnique identifiers - Demonstrate that the system assigns a unique identifier to each object ingested. Demonstrate two cases: (1) a unique identifier assigned to a digital object, which may be comprised of a set of component files, and (2) a unique identifier assigned to each of the component files of a digital object.7.1.1.15a, 7.1.1.15bTA handle is associated with each item. Each bitstream is uniquely identified. The original Handle ID is retained during re-ingest and a new Handle ID is added when exported data are re-ingested. However, if the replace option is used, the re-ingest will only replace the files without adding a new Handle ID.37.1.1.15bRelationships - Demonstrate that the system can represent a parent-child relationship between content items. Demonstrate two cases: (1) an object having multiple components (e.g., a document having multiple pages, each in a separate file), and (2) an object having multiple manifestations (e.g., an image having both TIFF and JPEG files).7.1.1.15bTItem=parent; bitstreams=children Bitstreams can be "bundled," though this is not apparent to users. HTML page can be designated as "primary"1.57.1.1.16Audit trail - Demonstrate that the system maintains an audit trail of all actions regarding receiving submissions (SIPs).7.1.1.16TInfo contained in log file but not easily usable.17.1.2 Ingest - Quality AssuranceT7.1.2.1Virus checking - By design analysis, confirm that the system performs automatic virus checking on submitted content files. 7.1.2.1TCould be handled by external tool as part of pre-ingest process07.1.2.2Transmission errors - Demonstrate that the system uses MD5, CRC, checksums, or some other bit error detection technique to validate that each data file submitted is received into the repository staging area without transmission errors. 7.1.2.2TMD5 computed and stored with each bitstream. SPER project added code to compute own MD5, which is part of SIP.17.1.2.3Submission validation - Demonstrate that the system verifies the validity of submitted content based on the following criteria: submitter; expected file format; file quality (e.g., actual format of file matches the filename extension, and content of file is well-formed); duplication (e.g., existence of object in the repository); completeness of metadata; completeness of file set (e.g., all expected files are included in the submission).7.1.2.3T07.1.2.4QA UI - Demonstrate that the system allows NLM staff to perform manual/visual quality assurance on staged SIPs via a user-friendly interface.7.1.2.4T27.1.2.5Reaction to QA errors - Demonstrate that the system can react to specified QA errors in two ways: (1) request that the producer correct and resubmit the content, or (2) automatically modify the submission (e.g., converting to a supported format).7.1.2.5T1 - Rejection email sent back to submitter. 2 - No automated way17.1.2.6File/batch accept/reject - Demonstrate that the system enables NLM staff to accept or reject submitted content (SIPs) at the file or batch level.7.1.2.6TFile review is manual (one x one). Batch review is not automated.1.57.1.2.7bError reports - Demonstrate that the system generates error reports for ingest quality assurance problems.7.1.2.7bTThe DSpace statistics reports show a count of the number of item rejections and rejection notifications. The reports do not classify reasons for rejection, and do not include the text reason entered by the rejecting reviewer. Successful and unsuccessful batch ingests are not included in the statistics reports.17.1.2.8Adjustable level of manual QC - By design analysis, confirm that the system has the ability to adjust the level of manual ingest quality control needed, based on the origin of the file.7.1.2.8T07.1.2.9Audit trail - Demonstrate that the system maintains an audit trail of all actions regarding ingest quality assurance.7.1.2.9TThe DSpace log records when items are submitted, approved, and rejected. Reasons for rejection are not recorded. Successful and unsuccessful batch ingests are logged.17.1.4 Ingest - Generate Descriptive Information / MetadataM7.1.4.1Additional metadata - Demonstrate the entry of additional metadata (e.g. subject headings, names, dates, curatorial descriptive metadata - evaluative information that explains why an object is important, whether it was part of a larger collection (e.g., an exhibit), etc.).7.1.4.1MRather clunky27.1.4.2Validate metadata - Demonstrate ability to validate specified metadata elements.7.1.4.2M07.1.4.4Metadata storage - Demonstrate that metadata is stored in the database in a manner that conforms to repository reformatting and linked to their corresponding objects via an identifier. o Demonstrates that basic descriptive metadata is also stored with the objects (e.g., unique identifier, title and date stored in the TIFF header) so that the objects can still be identified in the event that information in the database is corrupted. o See Appendix D for examples of TIFF header metadata requirements. (Use of external tool probable)7.1.4.4MFirst bullet - 2; second bullet - 227.1.4.5Required descriptive elements - Demonstrate the ability to recognize required descriptive elements.7.1.4.5Mwould need an external tool; could write a program to do this17.1.4.7Audit trail - Demonstrate the creation of an audit trail of all actions.7.1.4.7M17.1.3 Ingest - Generate AIPNote 3P7.1.5 Ingest - Coordinate UpdatesNote 3P7.2.1 Archival Storage - Receive DataNote 3P7.2.2 Archival Storage - Manage Storage HierarchyNote 3P7.2.3 Archival Storage - Replace MediaNote 3P7.2.4 Archival Storage - Error Checking and Disaster RecoveryNote 3P7.2.5 Archival Storage - Provide DataNote 3P7.3.1 Data Management - Administer DatabaseNote 3P7.3.2 Data Management - Administer Perform QueriesNote 3P7.3.3 Data Management - Generate ReportNote 3P7.3.4 Data Management - Receive Database UpdatesNote 3P7.4 AdministrationNote 3PP1 - Generate AIPPP1-1Generate AIP - Demonstrate the generation of AIPs from ingested SIPs that do not need normalization.7.1.3.1, 7.1.3.2, 7.1.3.3, 7.4.1PYes2P1-2Generate AIP with normalization - Demonstrate the generation of AIPs from ingested SIPs that need normalization - Transform an unsupported format to an accepted format (See Appendix B).7.1.3.1, 7.1.3.2, 7.1.3.3, 7.4.1PNO: No normalization and submission auditing (check the title field only).0P1-3Derivative files - Demonstrate the generation of AIPs that consist of master files and derivatives.7.1.3.6PYes1P1-4Master files - Demonstrate the generation of AIPs that consist of master files only.7.1.3.6PYes1P1-5Store AIP in archival storage - Demonstrate the ability to transfer AIPs to Archive Storage.7.1.5.1, 7.2.1.1, 7.2.1.2PYes2P1-6Store metadata in DB - Demonstrate the ability to generate and transfer Descriptive Information (metadata) to Data Management Database. 7.1.5.2, 7.3.4.1PYes2P1-7Link metadata and objects - Demonstrate the ability to store identification information in the Data Management database and link digital objects in the Archive Storage.7.1.5.4PYes2P1-8Send confirmation - Demonstrate the ability to automatically send confirmation to ingest and/or receiver when AIP and metadata transfers are completed.7.1.5.1, 7.1.5.3, 7.2.1.3, 7.3.3.3PYes for manual ingest. Batch ingest has only on-screen confirmation and can optionally invoke workflow process. Batch ingest provides on-screen confirmation of item ingest; data shown includes all metadata values and bitstream file names. (Ed verified)2P1-9Send statistical reports - Demonstrate the ability to automatically send statistical reports to ingest and/or receivers when AIP and metadata transfers are completed.7.1.5.1, 7.1.5.3, 7.2.1.3, 7.3.3.3PNo for manual ingest. The existing DSpace statistics reports do not include counts for items ingested via batch ingest. (Ed verified.)0P1-10Send error reports - Demonstrate the ability to automatically send error reports to ingest and/or receivers when AIP and/or metadata transfers fail.7.1.5.1, 7.1.5.3, 7.2.1.3, 7.3.3.3PNo for manual ingest. Error reports are not sent for batch ingest. (Ed verified.)0P2 - Administer Archival Storage & DatabasePP2-1Monitor transfer integrity - Demonstrate the built-in function to automatically monitor and report if any AIPs and metadata are altered or corrupted during data transfer and media change (refresh or replace).7.2.2.1, 7.2.3.2, 7.2.4.1PYes. The DSpace Checksum Checker verifies that checksum of every bitstream file in the repository has not changed. The Checker can be configured to run regularly using the Unix cron. The Checker creates a log file that contains the results of the checksum checker run.2P2-2Check data/referential integrity - Demonstrate the built-in function to perform routine and special referential and data integrity checks (CRC or checksums) on files in the Archive Storage and Data Management Database.7.2.4.2, 7.3.1.1, 7.3.1.2, 7.4.4PData integrity checks (checksum) for data transfer but not for version upgrades and format migration (7.4.4.). Also no referential integrity checks (7.3.1.2).1P2-3Routine configuration for data/referential integrity - Demonstrate the ability to allow for routine configuration.7.2.4.2, 7.3.1.1, 7.3.1.2, 7.4.4PSee comments in P2-2.1P2-4Disaster recovery - Demonstrate the ability to allow for disaster recovery including data backup, off-site data storage, and data recovery.7.2.4.3PYes. Can be recovered from backup or exported data)2P2-5User views - Demonstrate the ability to allow for customized user views of the contents of the storage (create, maintain, and access).7.3.1.4PYes with external tools.2P2-6System CM - Demonstrate the ability to allow for configuration management of the system hardware and software.7.4.2PYes2P2-7Database CM - Demonstrate the ability to allow for configuration management of the Data Management Database such as table, schema definitions, etc.7.3.1.3PYes2P2-8Delete AIPs - Demonstrate the ability to allow the authorized staff to delete AIPs from the repository including: removing the digital object's files and retaining associated metadata, or removing both the files and metadata.7.4.3.4PYes2P2-9Coordinate AIP removal - Demonstrate the ability to generate an alert and coordinate the removal of an AIP with maintenance of metadata held in other systems.7.4.3.5PNo0P2-10File migrations - Demonstrate the ability to allow the authorized staff to schedule and perform file migrations or migration on request for batched and individual files by authorized staff.7.4.3.6PNo0P2-11Request DIPs for update - Demonstrate the ability to allow the authorized staff to request DIPs for file migrations and data updates.7.3.4.1, 7.3.4.2, 7.3.4.3, 7.4.3.1, 7.4.3.2, 7.4.6.2PYes. DIPs can be requested and exported. However, it provides no tools for file migration and data updates. 1P2-12Re-ingest updated DIPs - Demonstrate the ability to allow the authorized staff to reingest updated DIPs as SIPs.7.4.3.3PYes. Exported data can be re-ingested with a replacing option. Ed will verify whether the re-ingest will also remove a deleted file from an item.2P2-13Support query requests - Demonstrate the ability to receive, retrieve, display, and deliver data for query requests from other functions such as Ingest, Access, and Administration.7.3.2.1, 7.3.2.3, 7.4.6.1PYes2P2-14Query requests from different storage locations - Demonstrate the ability to handle query requests with required data to be sourced from different storage locations.7.3.2.2PYes. Files can be optionally stored on a network file system.2P2-15Queries against all metadata - Demonstrate the ability to run data queries against all metadata used to manage the repository.7.3.2.4PYes2P2-16Audit trial - Demonstrate the creation of an audit trail of all actions including who, when, how, what and where for Archive Storage and Data Management Database.7.1.3.4, 7.1.5.6, 7.2.1.4, 7.2.2.3, 7.2.5.2, 7.3.2.5, 7.3.3.7, 7.3.4.6, 7.4.3.7, 7.4.6.4PNo provenance for record update and no email/screen confirmation for delete/withdrawal.1P2-17Generate reports - Demonstrate the ability to receive, generate, display, and deliver management information reports and statistics such as summaries of repository holdings by category, summaries of updates by category, user codes, etc., usage statistics for access to repository holdings, and descriptive information for a specific AIP.7.3.3.1, 7.3.3.2, 7.3.3.5, 7.3.4.4PPerl was installed to enable DSpace's statistics tools to be exercised, and the reports were viewed by the entire working group. // Monthly and total repository lifetime reports can be generated that show the total number of archived items, but the items are not broken down into categories (e.g., collections, submitters). The total number of archived items shown in the report includes all items ingested via the web interface and by batch; the "items ingested" counts only those items ingested via the web interface (does not include items ingest by batch). Counts are shown for creation, update, and deletion of items, bitstreams, bundles, collection, and communities; but these counts are only for "all items," "all collections," etc. Updates to the metadata of items are not counted or otherwise reported. Counts are reported for total user logins, total item views, bitstream views, searches performed. User logins are also reported by userid. Items are identified that were viewed more than a certain number of times. Note: Some actions shown in the "All Actions Taken Report" were unclear.1P2-18Schedule reports - Demonstrate the ability to generate reports in an ad-hoc manner, automatically or to be triggered by a calendar or by a specific system event.7.3.3.4PThe Perl-based DSpace statistics report generator can be run manually by an administrator, or scheduled to run at any desired frequency (e.g., daily, weekly, monthly) using the Unix cron task scheduler. However, only two type of reports can be generated: total repository activity up through the current date/time, and monthly activity reports. DSpace can be configured so that reports can be viewed by all users, or only by administrators. 1P2-19Time period for reports - Demonstrate the ability to allow the user to specify a time period or set of time periods for reports and statistics.7.3.3.6PDSpace's Perl-based statistics and report generation tools only enable the creation of monthly reports.0P3 - Generate DIPPP3-1Generate DIP for access requests - Demonstrate the generation of DIPs by putting AIPs and Descriptive Information back together for access requests.7.1.5.5, 7.2.5.1, 7.4.6.2PYes2P3-2Generate DIP for object maintenance - Demonstrate the generation of DIPs by putting AIPs and Descriptive Information back together for content/metadata update, versions upgrades and format migration by authorized staff.7.4.6.2, 7.4.3PYes27.4.1 Administration - Negotiate Submission AgreementT7.4.1.1Manage submission agreements - Demonstrate that the system manages information regarding submission agreements: that it tracks negotiation status and written submission agreements, and that it maintains schedules. 7.4.1.1T07.4.1.2Edit submission agreements - Demonstrate that the system allows submission agreements to be edited, based on the access level of the user.7.4.1.2T07.4.1.5Terms of submission agreements - Demonstrate that the system stores the terms of submission agreements, and uses the terms to monitor, review, and process submissions. 7.4.1.5T07.4.1.6Audit trail - Demonstrate that the system maintains an audit trail of all actions related to submission agreements.7.4.1.6T07.4.2 Administration - Manage System ConfigurationT7.4.2.1Monitor repository functionality - Demonstrate that the system monitors the functionality of the entire repository.7.4.2.1TFunctions are monitored but not entire repository.07.4.2.2System configuration - By design analysis, confirm that the system maintains the integrity of the system configuration.7.4.2.2T07.4.2.3Audits operations - Demonstrate that the system audits system operations, performance, and usage.7.4.2.3TIn log file.27.4.2.4Data management information - Demonstrate that the system collects and can display system information concerning Data Management.7.4.2.4TStatistics reports show the number of items, communities, collections, bitstreams, and bundles that are created, updated, and deleted in each month, and totaled for all months of operation. Additional detailed information is collected in the log file, but no report is generated containing this detail. No information collected or reported on metadata updates. Reports don't breakdown activity by specific user, community, or collection.17.4.2.5Operational statistics - Demonstrate that the system collects and can display operational statistics concerning Archival Storage.7.4.2.5TStatistics reports show total number of items in archive, and number of items archived each month. Batch imported items are included in "total in archive", but not included in "items archived". No breakdowns by collection, community, user. No totals for bitstreams. Additional detailed information is recorded in the log file and history files, but no tool is currently available to report on this information.17.4.3 Administration - Archival Information Update7.4.5 Administration - Audit SubmissionT7.4.5.1Audits - Demonstrate that the system can support an audit procedure to verify that submissions (SIP or AIP) meet specified requirements of the repository. The audit method may be based on sampling, periodic review, or peer review. [See NLM DRD Functional Requirements document, section 7.4.5 for description of audit requirements.] (Also partially covered by 7.2.4.2)7.4.5.1T07.4.5.2Metadata audit - Demonstrate that the system can audit metadata as part of the audit procedure. 7.4.5.2T07.4.5.3Audit rejection - Demonstrate that the system can reject components of audited information packages, based on specified audit requirements.7.4.5.3T07.4.5.4Audit report - Demonstrate that the system can generate an audit report, based on the results of periodic audits of SIPs and AIPs.7.4.5.4T07.4.5.5Audit trail - Demonstrate that the system maintains an audit trail of all actions regarding the auditing of SIPs and AIPs.7.4.5.5T07.4.6 Administration - Activate RequestsP7.6.1 Access - Coordinate Access Activities - User AccessA7.6.1.1Manage user permissions - Demonstrate the access controls for multiple permission levels and user privileges.7.6.1.1ADiscrete admin accounts; authenticated users can be limited to specific functions or collections. Collections can be hidden from public (anonymous) view.27.6.1.2Manage user restrictions - Demonstrate multiple levels of access restrictions for NIH employees and general public based on licensing terms, embargo periods, IP range restrictions, workstation access, and other possible legal restrictions. 7.6.1.2, 7.6.1.3ANo built-in logic to tie access controls to licensing data. No built-in access controls based on IP ranges. Collections could be hidden from anonymous users via the Authorizations policies.17.6.1.4Manage user settings - Demonstrate access settings allow staff to add or edit descriptive metadata7.6.1.4A37.6.1.7Audit users - Demonstrate access mechanisms can identify individual users and maintain audit log of user actions. 7.6.1.7AMetadata edit actions are not logged in a useable way.07.6.1.5Perform maintenance tasks - Demonstrate maintenance access including adding new files, manipulating images, editing metadata, performing format conversions/migrations, and troubleshooting system problems.7.6.1.5AMaintenance actions demonstrated by Ed. Some can be through the UI, some are command-line only.17.6.1.6Manage system rights - Demonstrate ultimate system rights access for NLM system administrators and programmers.7.6.1.6AOCCS staff testing has demonstrated system-level access for both the system files and the Oracle schema.17.6.1 Access - Coordinate Access Activities - Rights/Data Control of ObjectsA7.6.1.8Manage access rights - Demonstrate access rights and conditions to materials and storage directories provide for a combinational of create/write; edit; read; delete privileges.7.6.1.8Avia Authorizations section37.6.1.9Manage metadata rights - Demonstrate access rights may be associated with the metadata relating to an individual object 7.6.1.9AAuthorizations do not apply to metadata, only to Communities, Collections, Items, Bundles and Bitstreams. Item metadata is always viewable.07.6.1.13Manage relationships - Demonstrate access rights and conditions can be inherited from a parent object to any child object. 7.6.1.13Avia Authorizations section37.6.1.14Manage relationships - Demonstrate access rights and conditions can be assigned to an object on an individual or group basis at same time.7.6.1.14Avia Authorizations section37.6.1.16Automated retrieval - Demonstrate objects in the repository are accessible for data mining or automated retrieval.7.6.1.16ADSpace does not internally facilitate automated retrieval of its objects, only the metatdata via OAI-PMH. Full-text indexing by external source may be facilitated through a Java API in the future (JSR-170).07.6.1.17Metadata access - Demonstrate access to deleted and retracted metadata is retained.7.6.1.17AMinimal audit history in a cumulative log file accessible via scripts, but history of metadata actions is sparse.07.6.1.18Metadata harvesting - Demonstrate metadata harvesting following the OAI-PMH guidelines. 7.6.1.18ADSpace will allow external hosts to harvest its metadata via OAI-PMH. It does not do harvesting (bring in metatdata).27.6.1.10Access rights - Demonstrate access rights and conditions of use are applied to each digital object and its related metadata and are machine readable and actionable. 7.6.1.10, 7.6.1.11ALicense can be associated with a Collection or a specific item. There is no logic triggered by the license, which is just an unstructured text file.17.6.1.12Access conditions - Demonstrate access conditions are specific to a digital object.7.6.1.12AOnly collection-level restriction - denial of read access to anonymous.07.6.1.15Free/Restricted access - Demonstrate free (items available via internal/external delivery mechanisms) and restricted access (access permission must be satisfy various criteria) status for objects, files, metadata, etc.7.6.1.15AVerified collection-level restriction via Authorizations (read access denied to anonymous users). No file-level restriction is available.17.6.1 Access - Coordinate Access Activities - Search and RetrievalA7.6.1.19508 compliance - Demonstrate the search interface is web-accessible and Section 508 compliant.7.6.1.19AUser interface is entirely web-based. Tested with Fangs and Accessibility Add-on in Firefox. Tables are used for layout, but alt tags may be input for images. Content scaled logically when CSS is disabled. Unable to validate HTML code.27.6.1.20Search features - Demonstrate search includes: metadata, full-text, standard boolean, proximity, "more like" this"7.6.1.20, 7.6.1.21, 7.6.1.22, 7.6.1.23, 7.6.1.24AAmong the features listed, only metadata and, probably, full-text, are supported. Searching across DSpace needs additional investigation and it isnt clear how much configuration of Lucene (the underlying search engine) can be done.17.6.1.25Search results display - Demonstrate search results display includes date sort; relevancy ranking; alpha by author or source. 7.6.1.25AHelp mentions category search - how?07.6.1.26Relevancy ranking - Demonstrate whether relevancy ranking can be manipulated via system as well as user defined settings. 7.6.1.26A07.6.1.29Federated search - Demonstrate federated searching of different repository sites.7.6.1.29A07.6.1.30Advanced search - Demonstrate advanced search includes search history; saved searches; saved citation lists/bibliographies; alerts; various functions and formats; dynamic selection of delivery media without recreating search query.7.6.1.30A07.6.1.31Display formats - Demonstrate a variety of standard display formats are provided and whether they are customizable by user7.6.1.31A07.6.1.32Alternate search interfaces - Demonstrate availability of alternate search interfaces for mechanisms such as handhelds and PDAs.7.6.1.32A07.6.1.33Object access - Demonstrate access to the appropriate copy of the identified item (text, image, video, etc.) 7.6.1.33AThe record does describe the bitstream formats, but doesn't suggest the "appropriate" one17.6.1.34Library holdings - Demonstrate integration of search results with library holdings.7.6.1.34A07.6.1.35Response time - Demonstrate acceptable response time. 7.6.1.35AGood so far, but with very limited content. SPER testing suggests response time may suffer with large data sets.17.6.1.36External search engines - Demonstrate searching by outside search engines such as usa.gov, Google, and Yahoo. 7.6.1.36ASeveral DSpace installations have been indexed by search engines.27.6.1.37External system access - Demonstrate external access to other repositories or systems performing web harvesting functions.7.6.1.37A27.6.1.38Language support - Demonstrate how multiple languages and non-Roman scripts are supported in search, retrieval and display. 7.6.1.38Ademonstrated display of Chinese characters. Verified search & retrieval using Feng Chia University DSpace instance.27.6.1.39Versioning - Demonstrate access to all versions of digital objects in the repository is provided. 7.6.1.39ANo versioning functionality present. Any and all parts of an item will be accessible, but no relationships between parts can be conveyed.07.6.1.40Search settings - Demonstrate system settings and user-defined settings in the search functions are provided. 7.6.1.40AOnly default system-provided search settings are offered, through regular and advanced search interface.07.6.2 Access - Generate DIPA7.6.2.1Integrate holdings - Demonstrate integration of search results with library holdings.7.6.2.1AOpen-URLs can be utilized on item pages for possibly OPAC querying against the DC metadata associated with the item.17.6.2.2Retrieval and notification - Demonstrate the generation function accepts a dissemination request, retrieves AIP from archival storage and moves a copy of the data to a staging area for further processing, and creates and sends a report request to data management to obtain appropriate metadata. 7.6.2.2, 7.6.2.3, 7.6.2.4A37.6.2.7Audit trail - Demonstrate an audit trail of all actions is created and stored. 7.6.2.7AInfo contained in log file but not easily usable.07.6.2.5Response and delivery - Demonstrate that the prepared DIP response is placed in the staging area and a message is generated and sent to Coordinate Access Activities that the DIP is ready for delivery. 7.6.2.5AThis aspect of OAIS is not currently modeled by DSpace. DSpace does not appear to use a staging area but serves requested content directly from the Asset Store.07.6.2.6Storage retrieval - Demonstrate that Generate function accesses data objects in staging storage and applies the requested processes if special processing is required.7.6.2.6ASee above.07.6.3 Access - Deliver ResponseA7.6.3.1Web-accessibility - Demonstrate the display interface is web-accessible. 7.6.3.1AChecked using Fangs and the Accessibility Checker Add-on. It uses tables for layout purposes, but was unable to validate the HTML output.17.6.3.2Downloading - Demonstrate export function that provides XML output for batch downloads7.6.3.2AMust be done through externally scripting07.6.3.3Saving content - Demonstrate users are allowed to save digital content to a hard-drive, e-mail, and/or save search results. 7.6.3.3ADocuments may be downloaded. There does not appear to be a function for emailing or saving search results.17.6.3.5System notification - Demonstrate a confirmation message is returned to the Coordinate Access Activities section after response has been sent.7.6.3.5AThis aspect of OAIS is not currently modeled by DSpace. 07.6.3.6Audit trail - Demonstrate an audit trail of all actions is created and stored.7.6.3.6AInfo contained in log file but not easily usable.07.6.3.4Response request - Demonstrate a response request is received from Coordinate Access Activities 7.6.3.4ADemonstrated retrieval of objects via the UI without issue.28.1 Metadata RequirementsM8.1.1Metadata formats - Demonstrate that the system can accept metadata associated with objects in at least the following formats: All NLM DTDs, Dublin Core, MARC21, MARCXML, ONIX, MODS, EAD, TEI. 8.1.1M/TDoes accept it but minimally1 (M & T)8.1.2Metadata checks - Demonstrate the built-in checks on the incoming metadata. Records not containing the minimally defined set of fields should be flagged as problems, either to be returned to the submitter, or sent locally for metadata enhancement. 8.1.2MBatch - 0; manual - 10-18.1.5Metadata updates - Demonstrate the ability to allow for metadata updates. 8.1.5MRather clunky28.1.6aMetadata search and display - Demonstrate the ability to search and display metadata (use of external tool possible). 8.1.6aM28.1.8PREMIS - Demonstrate standards compliance for PREMIS (use of external tool possible). 8.1.8M/T0 (M & T)8.1.9METS - Demonstrate standards compliance for METS (use of external tool possible). 8.1.9M/TOnly exports collections/files in METS (via command line, not the web interface) and is working on METS import capability. 1 (M & T)App ADescriptive metadata - Demonstrate that the minimum descriptive metadata requirements described in Appendix A are accepted. App AM29.1 Additional Technical Infrastructure RequirementsT9.1.1OAI-PMH - Demonstrate that the system can respond to OAI-PMH requests as a data provider. 9.1.1TDSpace can be a provider but does not itself harvest and incorporate other data. Key functions: identify (handshake), listsets (list of collections), listidentifiers (list of IDs), listmetadataformat (list of metadata formats), listrecords (metadata only, no bit stream), etc.29.1.2Z39.50 - By design analysis, confirm that the system can respond to data requests using the Z39.50 standard.9.1.2T09.1.3SRU/SRW - By design analysis, confirm that the system can respond to data requests using the SRU and SRW data access standards.9.1.3T09.1.4SOAP - Demonstrate that the system can respond to web service requests using SOAP. 9.1.4T09.1.5UNICODE - Demonstrate that the system supports UNICODE.9.1.5T39.1.6OpenURL - By design analysis, confirm that the system is compliant with OpenURL.9.1.6T09.1.7Z39.87 - By design analysis, confirm that the system supports the Z39.87 image metadata standard.9.1.7T0Notes:1. Subgroups: A=Access, M=Metadata, P=Preservation, T=Technical Infrastructure2. Score indicates the extent to which the test element could be demonstrated: 0=None, 1=Low, 2=Moderate, 3=High3. Preservation tests - These sections of the functional requirements are covered by Test Plan sections P1, P2, and P3, which were defined by the Preservation subgroup to facilitate testing.4. Test elements having blue background are the subject of outstanding questions from the Access subgroup.10. Additional Observations10.1Back button on browser cannot function as a navigation tool all the time, and there is no other navigation tool. (KK)10.2Files are just listed in the order they were ingested and cannot be sorted by item (KK).10.3Sub-community hierarchies get lost in the collection selection window during submission (FK).10.4Batch ingest does allow customized licenses to be included for different items (EL).10.5Internal errors were generated in the following instances: 1. When more than one user to edit a record simultaneously. The record does not appear to be locked and DSpace generates internal system errors (JM, DB). 2. While trying to edit policies for a collection (FK) 10.6DSpace creates two XML files for item(s) containing both DC and NLM/DC metadata (such as permanence) during the export process. The dublincore.xml for all DC elements and metadata_nlm.xml for all NLM/DC elements. (EL)10.7DSpace tracks every action as an entry in a text-based log file but the log file doesnt reveal the specific action taken. The History file, on the other hand, records more specific details than the log file but some of the entries dont seem related to the actual action. For example, adding a subject and modifying an item type are recorded as updated bit streams and updated bundles in the history file. No tools are provided to access the history file. We should check with the DSpace community to see if there are any available tools already. (EL) Appendix D DigiTool Testing Results Consolidated Digital Repository Test Plan Last updated: June 13, 2008Source Require-mentsSub- group See Note 1DigiTool 3.0 TestsTest IDTest Plan ElementTest Procedure and ResultsScore (0-3) Note 2Notes7.1.1 Ingest - Receive SubmissionT7.1.1.7File types - Demonstrate that the system can ingest content in all the file formats listed as "supported" in Appendix B of the NLM DR Functional Requirements document (plus MP3 and JPEG2000), specifically: MARC, PDF, Postscript, AIFF, MPEG audio, WAV, MP3, GIF, JPEG, JPEG2000, PNG, TIFF, HTML, text, RTF, XML, MPEG. Demonstrate that the system can ingest the following types of content: articles, journals, images, monographs, audio files, video files, websites, numeric data, text files, and databases. Conduct this test element by ingesting the set of files listed in the Test File spreadsheet. (The files listed in this spreadsheet contain examples of all the file formats, and all the content types identified above.)7.1.1.7 7.1.1.9TCan automatically create thumbnails when ingesting JPG2000, PDF. (Some initial PDF ingest tests failed to produce thumbnails due to unusual PDF format.) 3 Answer was received to Question QT4.7.1.1.1Manual review - Demonstrate that the system has the capability to require that submitted content be manually reviewed before it is accepted into the repository. Demonstrate that the system maintains submitted content in a staging area before it is accepted. Demonstrate that the system notifies a reviewer when new content is ready for review. (Also see tests for 7.1.4.1, 7.1.4.2, and 8.1.2.)7.1.1.1T37.1.1.2Review and acceptance workflow - Demonstrate that the system supports a workflow for the review and acceptance of submitted content. Demonstrate that the workflow includes the following functions: a - Receive and track content from producers; b - Validate content based on submitter, expected format, file quality, duplication, and completeness; c - Normalize content by converting content into a supported format for final ingestion into the repository; d - Human review of content; e - Acceptance or rejection of content or file format. 7.1.1.2, 7.1.1.10Ta - yes b - no c - no d - yes e - yes27.1.1.3Reason for rejection - Demonstrate that the system records a set of identifying information or metadata that describes the reason for the rejection of submitted content. Demonstrate two cases: (1) automatic rejection, and (2) rejection by a human reviewer.7.1.1.3T1 - no 2 - maybe - needs further testing17.1.1.4Rejection filter - Demonstrate that the system allows the creation of a filter that can be used to automatically reject submitted content. (This capability will eliminate the need for manual review of some submissions and resubmissions.)7.1.1.4TThis is not filter based but rather template based17.1.1.5Rejection notification - Demonstrate that the system can notify the producer or donor when submitted content is rejected. Demonstrate two cases: (1) notification after immediate rejection by an automated process, and (2) notification after rejection by manual review.7.1.1.5, 7.1.1.11TFailure indication (instead of "success") upon immediate rejection.1 (7.1.1.8)Metadata types - Demonstrate that the system can ingest content with associated metadata in the following formats: all NLM DTDs, Dublin Core, MARC21, MARCXML, ONIX, MODS, EAD, TEI, PREMIS, METS. (NOTE: This test is covered by tests 8.1.1, 8.1.8, and 8.1.9)7.1.1.8, 8.1.1, 8.1.8, 8.1.9M/TT=2.5 M=2.57.1.1.10Format conversion - Demonstrate that the system has the capability to convert the format of a file being ingested to a desired supported format. As a test case, demonstrate that a WAV file can be converted to MP3 format when it is ingested. (An external tool may be needed to perform the conversion. If this is the case, demonstrate that the system can invoke the required external tool.) 7.1.1.10, 7.1.1.2TCan automatically create JPG and JP2 when ingesting TIFF. Can automatically create JPG when ingesting JP2. Can automatically create JPG thumbnail when ingesting JP2 and PDF. Can add other external file converters.2Answer was received to Question QT17.1.1.12Resubmission - Demonstrate that the system can ingest a SIP that is resubmitted after an error in the SIP was detected and corrected. Demonstrate two cases: the resubmission can occur after an error was detected in (1) the content of the SIP, and (2) the metadata of the SIP.7.1.1.12TFailed ingests can be rolled back, edited, and reingested.27.1.1.14Versions - Demonstrate that the system can store, track, and link multiple versions of a file.7.1.1.14TAlternate manifestations can be created but there are no "Versions"07.1.1.15aUnique identifiers - Demonstrate that the system assigns a unique identifier to each object ingested. Demonstrate two cases: (1) a unique identifier assigned to a digital object, which may be comprised of a set of component files, and (2) a unique identifier assigned to each of the component files of a digital object.7.1.1.15a, 7.1.1.15bT37.1.1.15bRelationships - Demonstrate that the system can represent a parent-child relationship between content items. Demonstrate two cases: (1) an object having multiple components (e.g., a document having multiple pages, each in a separate file), and (2) an object having multiple manifestations (e.g., an image having both TIFF and JPEG files).7.1.1.15bT37.1.1.16Audit trail - Demonstrate that the system maintains an audit trail of all actions regarding receiving submissions (SIPs).7.1.1.16T2.57.1.2 Ingest - Quality AssuranceT7.1.2.1Virus checking - By design analysis, confirm that the system performs automatic virus checking on submitted content files. 7.1.2.1T07.1.2.2Transmission errors - Demonstrate that the system uses MD5, CRC, checksums, or some other bit error detection technique to validate that each data file submitted is received into the repository staging area without transmission errors. 7.1.2.2TMD5 is created during ingest and is saved with the file. However, an MD5 generated pre-ingest cannot be compared with the DigiTool-created MD5 to verify that transmission errors have not occurred.1Answer was received to Question QT2.7.1.2.3Submission validation - Demonstrate that the system verifies the validity of submitted content based on the following criteria: submitter; expected file format; file quality (e.g., actual format of file matches the filename extension, and content of file is well-formed); duplication (e.g., existence of object in the repository); completeness of metadata; completeness of file set (e.g., all expected files are included in the submission).7.1.2.3TNo submission validation other than JHOVE checksum. Checksum done at ingest and no capability to compare externally provided checksum with that done during ingest.17.1.2.4QA UI - Demonstrate that the system allows NLM staff to perform manual/visual quality assurance on staged SIPs via a user-friendly interface.7.1.2.4T17.1.2.5Reaction to QA errors - Demonstrate that the system can react to specified QA errors in two ways: (1) request that the producer correct and resubmit the content, or (2) automatically modify the submission (e.g., converting to a supported format).7.1.2.5TAfter failed ingest user can rollback, edit, and resubmit. No automatic modifications performed.17.1.2.6File/batch accept/reject - Demonstrate that the system enables NLM staff to accept or reject submitted content (SIPs) at the file or batch level.7.1.2.6T1.57.1.2.7bError reports - Demonstrate that the system generates error reports for ingest quality assurance problems.7.1.2.7bT07.1.2.8Adjustable level of manual QC - By design analysis, confirm that the system has the ability to adjust the level of manual ingest quality control needed, based on the origin of the file.7.1.2.8T07.1.2.9Audit trail - Demonstrate that the system maintains an audit trail of all actions regarding ingest quality assurance.7.1.2.9T07.1.4 Ingest - Generate Descriptive Information / MetadataM7.1.4.1Additional metadata - Demonstrate the entry of additional metadata (e.g. subject headings, names, dates, curatorial descriptive metadata - evaluative information that explains why an object is important, whether it was part of a larger collection (e.g., an exhibit), etc.).7.1.4.1M37.1.4.2Validate metadata - Demonstrate ability to validate specified metadata elements.7.1.4.2M1.57.1.4.4Metadata storage - Demonstrate that metadata is stored in the database in a manner that conforms to repository reformatting and linked to their corresponding objects via an identifier. o Demonstrates that basic descriptive metadata is also stored with the objects (e.g., unique identifier, title and date stored in the TIFF header) so that the objects can still be identified in the event that information in the database is corrupted. o See Appendix D for examples of TIFF header metadata requirements. (Use of external tool probable)7.1.4.4M37.1.4.5Required descriptive elements - Demonstrate the ability to recognize required descriptive elements.7.1.4.5M37.1.4.7Audit trail - Demonstrate the creation of an audit trail of all actions.7.1.4.7M17.1.3 Ingest - Generate AIPNote 3P7.1.5 Ingest - Coordinate UpdatesNote 3P7.2.1 Archival Storage - Receive DataNote 3P7.2.2 Archival Storage - Manage Storage HierarchyNote 3P7.2.3 Archival Storage - Replace MediaNote 3P7.2.4 Archival Storage - Error Checking and Disaster RecoveryNote 3P7.2.5 Archival Storage - Provide DataNote 3P7.3.1 Data Management - Administer DatabaseNote 3P7.3.2 Data Management - Administer Perform QueriesNote 3P7.3.3 Data Management - Generate ReportNote 3P7.3.4 Data Management - Receive Database UpdatesNote 3P7.4 AdministrationNote 3PP1 - Generate AIPPP1-1Generate AIP - Demonstrate the generation of AIPs from ingested SIPs that do not need normalization.7.1.3.1, 7.1.3.2, 7.1.3.3, 7.4.1PCan generate an XML-based digital entity which contains points to link all objects and metadata but not physical AIP package.2P1-2Generate AIP with normalization - Demonstrate the generation of AIPs from ingested SIPs that need normalization - Transform an unsupported format to an accepted format (See Appendix B).7.1.3.1, 7.1.3.2, 7.1.3.3, 7.4.1PNo normalization.0P1-3Derivative files - Demonstrate the generation of AIPs that consist of master files and derivatives.7.1.3.6PCan convert a file from TIFF to JP2 or from TIFF/JP2 to JPEG. Can also generate JP2 thumbnail.1.5P1-4Master files - Demonstrate the generation of AIPs that consist of master files only.7.1.3.6PQP1: How does DigiTool manage manifestation relationships and identify which is the master that may or may not be in TIFF? Opher: Masters are handled in two contexts: (1) a preservation context, where the preservation_level field of the digital entity can be set to a value designated for masters (typically "Preservation Master" or "High") and used to differentiate between storage rules; (2) an application context, where the usage_type field of the digital entity (e. g. "main", "archive") can determine if the object would be delivered.2P1-5Store AIP in archival storage - Demonstrate the ability to transfer AIPs to Archive Storage.7.1.5.1, 7.2.1.1, 7.2.1.2PSee P1-12P1-6Store metadata in DB - Demonstrate the ability to generate and transfer Descriptive Information (metadata) to Data Management Database. 7.1.5.2, 7.3.4.1PGenerate (extract) and transfer.3P1-7Link metadata and objects - Demonstrate the ability to store identification information in the Data Management database and link digital objects in the Archive Storage.7.1.5.4PYes3P1-8Send confirmation - Demonstrate the ability to automatically send confirmation to ingest and/or receiver when AIP and metadata transfers are completed.7.1.5.1, 7.1.5.3, 7.2.1.3, 7.3.3.3PView in Success/Failed log on screen only. QP2: Can DigiTool send confirmation in an email to receivers? Opher: view logs and folder status of ingests at all phases through the web module, but emails are not sent.1P1-9Send statistical reports - Demonstrate the ability to automatically send statistical reports to ingest and/or receivers when AIP and metadata transfers are completed.7.1.5.1, 7.1.5.3, 7.2.1.3, 7.3.3.3PHas to click on each ingest ID to view details in the Success/Failed log. QP3: Can DigiTool send statistical reports (or along with the confirmation) in an email to receivers? Opher: view logs and folder status of ingests at all phases through the web module, but emails are not sent.1P1-10Send error reports - Demonstrate the ability to automatically send error reports to ingest and/or receivers when AIP and/or metadata transfers fail.7.1.5.1, 7.1.5.3, 7.2.1.3, 7.3.3.3POnly indicated in the Failed log. QP4: Why is there a rollback icon for a failed ingest in the Failed log? Does a failed one get ingested anyway? Opher: Yes in certain cases ingests partially fail (e. g. not all tasks could be 100% completed) but digital entities are created, and the rollback allows for the staff to analyze the problem, correct the cause for the partial failures, and re-ingest.1P2 - Administer Archival Storage & DatabasePP2-1Monitor transfer integrity - Demonstrate the built-in function to automatically monitor and report if any AIPs and metadata are altered or corrupted during data transfer and media change (refresh or replace).7.2.2.1, 7.2.3.2, 7.2.4.1PQP5 (Same as QT2 from Ed): Does DigiTool compare the checksum that is generated before the ingest with the one that is generated after the ingest? Opher: DigiTool creates a file-level checksum during ingest and can check the validity of this checksum of repository items as an ongoing post-ingest maintenance procedure. This procedure only supports checksums generated during the ingest, not prior to it.2P2-2Check data/referential integrity - Demonstrate the built-in function to perform routine and special referential and data integrity checks (CRC or checksums) on files in the Archive Storage and Data Management Database.7.2.4.2, 7.3.1.1, 7.3.1.2, 7.4.4PNo referential integrity check.1P2-3Routine configuration for data/referential integrity - Demonstrate the ability to allow for routine configuration.7.2.4.2, 7.3.1.1, 7.3.1.2, 7.4.4PNo referential integrity check.1P2-4Disaster recovery - Demonstrate the ability to allow for disaster recovery including data backup, off-site data storage, and data recovery.7.2.4.3PQP6: Can we reingest exported files for data recovery to recreate the repository? Opher: Yes - the entire repository (or parts of it) can be exported as digital entities (with respective file streams) to be re-ingested.2P2-5User views - Demonstrate the ability to allow for customized user views of the contents of the storage (create, maintain, and access).7.3.1.4PNot with external tool either.0P2-6System CM - Demonstrate the ability to allow for configuration management of the system hardware and software.7.4.2PLimited/restricted local control.1.5P2-7Database CM - Demonstrate the ability to allow for configuration management of the Data Management Database such as table, schema definitions, etc.7.3.1.3PNo database table or schema changes.0P2-8Delete AIPs - Demonstrate the ability to allow the authorized staff to delete AIPs from the repository including: removing the digital object's files and retaining associated metadata, or removing both the files and metadata.7.4.3.4PYes with rollback function.3P2-9Coordinate AIP removal - Demonstrate the ability to generate an alert and coordinate the removal of an AIP with maintenance of metadata held in other systems.7.4.3.5PNo alert.0P2-10File migrations - Demonstrate the ability to allow the authorized staff to schedule and perform file migrations or migration on request for batched and individual files by authorized staff.7.4.3.6PQP7: How to schedule and perform file migration and migration on request for batched or individual files? Opher: Filestreams for individual objects can be exported, imported, deleted or replaced using the Meditor. Batch migrations cannot be performed. 0P2-11Request DIPs for update - Demonstrate the ability to allow the authorized staff to request DIPs for file migrations and data updates.7.3.4.1, 7.3.4.2, 7.3.4.3, 7.4.3.1, 7.4.3.2, 7.4.6.2PQP8: How to request DIPs for file migrations and data updates? Opher: This can be done on an individual basis only. Objects can be "pulled" from the repository into the Meditor in various ways for filestream maintenance. 1P2-12Re-ingest updated DIPs - Demonstrate the ability to allow the authorized staff to reingest updated DIPs as SIPs.7.4.3.3PNo duplication check or overwrite option.1P2-13Support query requests - Demonstrate the ability to receive, retrieve, display, and deliver data for query requests from other functions such as Ingest, Access, and Administration.7.3.2.1, 7.3.2.3, 7.4.6.1PYes.2P2-14Query requests from different storage locations - Demonstrate the ability to handle query requests with required data to be sourced from different storage locations.7.3.2.2PNFS or URL retrieval.2.5P2-15Queries against all metadata - Demonstrate the ability to run data queries against all metadata used to manage the repository.7.3.2.4PYes2.5P2-16Audit trial - Demonstrate the creation of an audit trail of all actions including who, when, how, what and where for Archive Storage and Data Management Database.7.1.3.4, 7.1.5.6, 7.2.1.4, 7.2.2.3, 7.2.5.2, 7.3.2.5, 7.3.3.7, 7.3.4.6, 7.4.3.7, 7.4.6.4PQP9: Does DigiTool keep an audit trail for all actions including who, when, how, how and where for the archive storage and database? Opher: Such preservation-oriented needs are better addressed by our Preservation system. In DigiTool, the History metadata provides a partial audit trail. 1P2-17Generate reports - Demonstrate the ability to receive, generate, display, and deliver management information reports and statistics such as summaries of repository holdings by category, summaries of updates by category, user codes, etc., usage statistics for access to repository holdings, and descriptive information for a specific AIP.7.3.3.1, 7.3.3.2, 7.3.3.5, 7.3.4.4PQP10: Which specific reports and statistics can be generated? Opher: Currently: Repository DE and stream count, Depositor Statistics Reports, Digital Entities Viewing Reports. We are also planning on implementing the BIRT reporting system in DigiTool later in 2008 this will allow for more extensive reporting.1P2-18Schedule reports - Demonstrate the ability to generate reports in an ad-hoc manner, automatically or to be triggered by a calendar or by a specific system event.7.3.3.4PQP11: Need clarification on how available reports/statistics can be generated in an ad-hoc manner, automatically or to be triggered by a calendar or by a specific system event. Opher: These can be run ad-hoc (immediately or postponed), and can be scheduled, by calendar, for ongoing running using cron. 2P2-19Time period for reports - Demonstrate the ability to allow the user to specify a time period or set of time periods for reports and statistics.7.3.3.6PQP12: Need clarification on how a user can specify a time period or set of time periods for reports and statistics. Opher: DE viewing reports can be filtered by date. With the implementations of BIRT this will be expanded.1P3 - Generate DIPPP3-1Generate DIP for access requests - Demonstrate the generation of DIPs by putting AIPs and Descriptive Information back together for access requests.7.1.5.5, 7.2.5.1, 7.4.6.2PYes2P3-2Generate DIP for object maintenance - Demonstrate the generation of DIPs by putting AIPs and Descriptive Information back together for content/metadata update, versions upgrades and format migration by authorized staff.7.4.6.2, 7.4.3PPending for answers to QP6, QP7 and QP8.27.4.1 Administration - Negotiate Submission AgreementT7.4.1.1Manage submission agreements - Demonstrate that the system manages information regarding submission agreements: that it tracks negotiation status and written submission agreements, and that it maintains schedules. 7.4.1.1T07.4.1.2Edit submission agreements - Demonstrate that the system allows submission agreements to be edited, based on the access level of the user.7.4.1.2T07.4.1.5Terms of submission agreements - Demonstrate that the system stores the terms of submission agreements, and uses the terms to monitor, review, and process submissions. 7.4.1.5T07.4.1.6Audit trail - Demonstrate that the system maintains an audit trail of all actions related to submission agreements.7.4.1.6T07.4.2 Administration - Manage System ConfigurationT7.4.2.1Monitor repository functionality - Demonstrate that the system monitors the functionality of the entire repository.7.4.2.1T07.4.2.2System configuration - By design analysis, confirm that the system maintains the integrity of the system configuration.7.4.2.2T07.4.2.3Audits operations - Demonstrate that the system audits system operations, performance, and usage.7.4.2.3T0BIRT reporting system coming late 20087.4.2.4Data management information - Demonstrate that the system collects and can display system information concerning Data Management.7.4.2.4T07.4.2.5Operational statistics - Demonstrate that the system collects and can display operational statistics concerning Archival Storage.7.4.2.5TMust use SQL reporting07.4.3 Administration - Archival Information Update7.4.5 Administration - Audit SubmissionT7.4.5.1Audits - Demonstrate that the system can support an audit procedure to verify that submissions (SIP or AIP) meet specified requirements of the repository. The audit method may be based on sampling, periodic review, or peer review. [See NLM DRD Functional Requirements document, section 7.4.5 for description of audit requirements.] (Also partially covered by 7.2.4.2)7.4.5.1TEx Libris sees audit procedures as a preservation concern, and will be provided in the new Preservation tool (DPS).0Answer was received to Question QT3. 7.4.5.2Metadata audit - Demonstrate that the system can audit metadata as part of the audit procedure. 7.4.5.2T07.4.5.3Audit rejection - Demonstrate that the system can reject components of audited information packages, based on specified audit requirements.7.4.5.3T07.4.5.4Audit report - Demonstrate that the system can generate an audit report, based on the results of periodic audits of SIPs and AIPs.7.4.5.4T07.4.5.5Audit trail - Demonstrate that the system maintains an audit trail of all actions regarding the auditing of SIPs and AIPs.7.4.5.5T07.4.6 Administration - Activate RequestsP7.6.1 Access - Coordinate Access Activities - User AccessA7.6.1.1Manage user permissions - Demonstrate the access controls for multiple permission levels and user privileges.7.6.1.1AGood, but not robust. Staff Privileges configuration governs a fairly granular list of rights for Staff Users, Admin Users. Automated patron registration and authentication possible using LDAP.27.6.1.2Manage user restrictions - Demonstrate multiple levels of access restrictions for NIH employees and general public based on licensing terms, embargo periods, IP range restrictions, workstation access, and other possible legal restrictions. 7.6.1.2, 7.6.1.3AEmbargo period - Kaplan explained they hoped to do more with this feature.27.6.1.4Manage user settings - Demonstrate access settings allow staff to add or edit descriptive metadata7.6.1.4AMeditor is used to add or edit metadata.27.6.1.7Audit users - Demonstrate access mechanisms can identify individual users and maintain audit log of user actions. 7.6.1.7AAudit trails were detailed and human-readable37.6.1.5Perform maintenance tasks - Demonstrate maintenance access including adding new files, manipulating images, editing metadata, performing format conversions/migrations, and troubleshooting system problems.7.6.1.5ASome of these functions are also addressed below. File and metadata access is provided via web interface and Meditor client.27.6.1.6Manage system rights - Demonstrate ultimate system rights access for NLM system administrators and programmers.7.6.1.6AQuestion for technical infrastructure? Too ambiguous for Access group to answer.?7.6.1 Access - Coordinate Access Activities - Rights/Data Control of ObjectsA7.6.1.8Manage access rights - Demonstrate access rights and conditions to materials and storage directories provide for a combinational of create/write; edit; read; delete privileges.7.6.1.8AHow are storage directories integrated into DigiTool? If deleted in DigiTool does it delete from servers? 37.6.1.9Manage metadata rights - Demonstrate access rights may be associated with the metadata relating to an individual object 7.6.1.9AEmbargo information is part of metadata - how is this done? 27.6.1.13Manage relationships - Demonstrate access rights and conditions can be inherited from a parent object to any child object. 7.6.1.13AManifestations and complex objects can share descriptive metadata and/or usage rights.27.6.1.14Manage relationships - Demonstrate access rights and conditions can be assigned to an object on an individual or group basis at same time.7.6.1.14ABatch metadata changes can be performed via management jobs (but _not_ via Object Manager).27.6.1.16Automated retrieval - Demonstrate objects in the repository are accessible for data mining or automated retrieval.7.6.1.16AOpen URL compliant, OAI-PMH for metadata retrieval. Resource Discovery has full-text searching, but no built-in data mining services.17.6.1.17Metadata access - Demonstrate access to deleted and retracted metadata is retained.7.6.1.17AOnce it's gone, it's gone.07.6.1.18Metadata harvesting - Demonstrate metadata harvesting following the OAI-PMH guidelines. 7.6.1.18ADigiTool will allow external hosts to harvest its metadata via OAI-PMH. It does not do harvesting (bring in metatdata) using this protocol but can do so via Z39.50.27.6.1.10Access rights - Demonstrate access rights and conditions of use are applied to each digital object and its related metadata and are machine readable and actionable. 7.6.1.10, 7.6.1.11ARights and use conditions can be recorded into controlled metadata fields such as Usage Type, which can restrict harvesting into Silos.27.6.1.12Access conditions - Demonstrate access conditions are specific to a digital object.7.6.1.12AViewable in Object Manager37.6.1.15Free/Restricted access - Demonstrate free (items available via internal/external delivery mechanisms) and restricted access (access permission must be satisfy various criteria) status for objects, files, metadata, etc.7.6.1.15AViewable in Object Manager, but embargo is not sophisticated27.6.1 Access - Coordinate Access Activities - Search and RetrievalA7.6.1.19508 compliance - Demonstrate the search interface is web-accessible and Section 508 compliant.7.6.1.19AGood faith effort well-documented by ExLibris. Meditor is likely to be weak in this area, but it's on the way out.27.6.1.20Search features - Demonstrate search includes: metadata, full-text, standard boolean, proximity, "more like" this"7.6.1.20, 7.6.1.21, 7.6.1.22, 7.6.1.23, 7.6.1.24ANo proximity and no "More like this", but Object Manager has a controlled metadata search.27.6.1.25Search results display - Demonstrate search results display includes date sort; relevancy ranking; alpha by author or source. 7.6.1.25ANo date ranking, but it is promised in an upcoming service pack.27.6.1.26Relevancy ranking - Demonstrate whether relevancy ranking can be manipulated via system as well as user defined settings. 7.6.1.26AUnclear how relevancy is determined; cannot be modified.17.6.1.29Federated search - Demonstrate federated searching of different repository sites.7.6.1.29AResource Discovery searches across admin units by harvesting content into silos.27.6.1.30Advanced search - Demonstrate advanced search includes search history; saved searches; saved citation lists/bibliographies; alerts; various functions and formats; dynamic selection of delivery media without recreating search query.7.6.1.30ASearch can be refined by adding additional values (using AND, OR or WITHOUT). Search history available during session. Can save results to "my space" (one object at a time).17.6.1.31Display formats - Demonstrate a variety of standard display formats are provided and whether they are customizable by user7.6.1.31AA limited number of Resource Discovery default Preferences can be set by user.17.6.1.32Alternate search interfaces - Demonstrate availability of alternate search interfaces for mechanisms such as handhelds and PDAs.7.6.1.32A07.6.1.33Object access - Demonstrate access to the appropriate copy of the identified item (text, image, video, etc.) 7.6.1.33AMetadata can indicate the "use" manifestation of an object.17.6.1.34Library holdings - Demonstrate integration of search results with library holdings.7.6.1.34ACan be done using Primo, but not internal to DigiTool.07.6.1.35Response time - Demonstrate acceptable response time. 7.6.1.35AResponse time in NLM development environment can be very slow, although ExLibris demos generally showed acceptable response17.6.1.36External search engines - Demonstrate searching by outside search engines such as usa.gov, Google, and Yahoo. 7.6.1.36AExLibris is in the process of making search-engine friendly site maps - will be introduced in a service pack. (Commercial search engines do not want to spider via OAI-PMH.)17.6.1.37External system access - Demonstrate external access to other repositories or systems performing web harvesting functions.7.6.1.37Avia OAI-PMH and Z39.5027.6.1.38Language support - Demonstrate how multiple languages and non-Roman scripts are supported in search, retrieval and display. 7.6.1.38AResource Discovery has multiple languages, Unicode support27.6.1.39Versioning - Demonstrate access to all versions of digital objects in the repository is provided. 7.6.1.39AAll objects / manifestations can be provided, with metadata distinguishing between manifestations.27.6.1.40Search settings - Demonstrate system settings and user-defined settings in the search functions are provided. 7.6.1.40AOnly default system-provided search settings are offered, through regular and advanced search interface.07.6.2 Access - Generate DIPA7.6.2.1Integrate holdings - Demonstrate integration of search results with library holdings.7.6.2.1ACould be done via Primo, but not internal to DigiTool07.6.2.2Retrieval and notification - Demonstrate the generation function accepts a dissemination request, retrieves AIP from archival storage and moves a copy of the data to a staging area for further processing, and creates and sends a report request to data management to obtain appropriate metadata. 7.6.2.2, 7.6.2.3, 7.6.2.4AAIP and DIP are conceptual in DigiTool, but system provides the bitstream through a pre-determined viewer, and metadata is also provided.27.6.2.7Audit trail - Demonstrate an audit trail of all actions is created and stored. 7.6.2.7AUsage reporting is available to administrators.17.6.2.5Response and delivery - Demonstrate that the prepared DIP response is placed in the staging area and a message is generated and sent to Coordinate Access Activities that the DIP is ready for delivery. 7.6.2.5AItems are already 'harvested' into the silo for public access - this is probably comparable to staging/delivery.27.6.2.6Storage retrieval - Demonstrate that Generate function accesses data objects in staging storage and applies the requested processes if special processing is required.7.6.2.6AAs above.27.6.3 Access - Deliver ResponseA7.6.3.1Web-accessibility - Demonstrate the display interface is web-accessible. 7.6.3.1AResource Discovery is completely web-based. Some object viewers are served through the browser, some objects rely on local PC software.37.6.3.2Downloading - Demonstrate export function that provides XML output for batch downloads7.6.3.2Ano batch downloading of objects available to end user, but comprehensive exporting available from management side.17.6.3.3Saving content - Demonstrate users are allowed to save digital content to a hard-drive, e-mail, and/or save search results. 7.6.3.3AUsers can save / email, add to e-shelf, SFX / Primo integration possible.37.6.3.5System notification - Demonstrate a confirmation message is returned to the Coordinate Access Activities section after response has been sent.7.6.3.5A07.6.3.6Audit trail - Demonstrate an audit trail of all actions is created and stored.7.6.3.6Ausage reporting is available to administrators.17.6.3.4Response request - Demonstrate a response request is received from Coordinate Access Activities 7.6.3.4Aif patron is authenticated, DigiTool can evaluate patron's rights before delivering content. Otherwise, Resource Discovery delivers according to anonymous rights.18.1 Metadata RequirementsM8.1.1Metadata formats - Demonstrate that the system can accept metadata associated with objects in at least the following formats: All NLM DTDs, Dublin Core, MARC21, MARCXML, ONIX, MODS, EAD, TEI. 8.1.1M/TMapping to DC onlyT=2 M=2TEI/EAD not that great8.1.2Metadata checks - Demonstrate the built-in checks on the incoming metadata. Records not containing the minimally defined set of fields should be flagged as problems, either to be returned to the submitter, or sent locally for metadata enhancement. 8.1.2MBatch=1; Manual = 21-28.1.5Metadata updates - Demonstrate the ability to allow for metadata updates. 8.1.5M38.1.6aMetadata search and display - Demonstrate the ability to search and display metadata (use of external tool possible). 8.1.6aM1.58.1.8PREMIS - Demonstrate standards compliance for PREMIS (use of external tool possible). 8.1.8M/TT=0 M=18.1.9METS - Demonstrate standards compliance for METS (use of external tool possible). 8.1.9M/TT=3 M=2App ADescriptive metadata - Demonstrate that the minimum descriptive metadata requirements described in Appendix A are accepted. App AM2.59.1 Additional Technical Infrastructure RequirementsT9.1.1OAI-PMH - Demonstrate that the system can respond to OAI-PMH requests as a data provider. 9.1.1TOAI data provider only.29.1.2Z39.50 - By design analysis, confirm that the system can respond to data requests using the Z39.50 standard.9.1.2T29.1.3SRU/SRW - By design analysis, confirm that the system can respond to data requests using the SRU and SRW data access standards.9.1.3T09.1.4SOAP - Demonstrate that the system can respond to web service requests using SOAP. 9.1.4T39.1.5UNICODE - Demonstrate that the system supports UNICODE.9.1.5T39.1.6OpenURL - By design analysis, confirm that the system is compliant with OpenURL.9.1.6T39.1.7Z39.87 - By design analysis, confirm that the system supports the Z39.87 image metadata standard.9.1.7T1.5Notes:1. Subgroups: A=Access, M=Metadata, P=Preservation, T=Technical Infrastructure2. Score indicates the extent to which the test element could be demonstrated: 0=None, 1=Low, 2=Moderate, 3=High3. Preservation tests - These sections of the functional requirements are covered by Test Plan sections P1, P2, and P3, which were defined by the Preservation subgroup to facilitate testing.4. Test elements having blue background are the subject of outstanding questions from the Access subgroup. Appendix E Fedora Testing Results Consolidated Digital Repository Test Plan Last updated: October 16, 2008Source Require-mentsSub- group See Note 1Fedora 2.2/Fez 2 Release Candidate 1 (Score reflects Fedora/Fez total)Test Procedure and ResultsScore (0-3) Note 2NotesTest IDTest Plan ElementFedoraFezBoth or Not Sure7.1.1 Ingest - Receive SubmissionT7.1.1.7File types - Demonstrate that the system can ingest content in all the file formats listed as "supported" in Appendix B of the NLM DR Functional Requirements document (plus MP3 and JPEG2000), specifically: MARC, PDF, Postscript, AIFF, MPEG audio, WAV, MP3, GIF, JPEG, JPEG2000, PNG, TIFF, HTML, text, RTF, XML, MPEG. Demonstrate that the system can ingest the following types of content: articles, journals, images, monographs, audio files, video files, websites, numeric data, text files, and databases. Conduct this test element by ingesting the set of files listed in the Test File spreadsheet. (The files listed in this spreadsheet contain examples of all the file formats, and all the content types identified above.)7.1.1.7 7.1.1.9T333Tests and demo examples show that all file types are supported.7.1.1.1Manual review - Demonstrate that the system has the capability to require that submitted content be manually reviewed before it is accepted into the repository. Demonstrate that the system maintains submitted content in a staging area before it is accepted. Demonstrate that the system notifies a reviewer when new content is ready for review. (Also see tests for 7.1.4.1, 7.1.4.2, and 8.1.2.)7.1.1.1T0 - Fedora provides no manual review. 1 - Fez can be configured with a workflow that includes manual review, but no notification is sent.17.1.1.2Review and acceptance workflow - Demonstrate that the system supports a workflow for the review and acceptance of submitted content. Demonstrate that the workflow includes the following functions: a - Receive and track content from producers; b - Validate content based on submitter, expected format, file quality, duplication, and completeness; c - Normalize content by converting content into a supported format for final ingestion into the repository; d - Human review of content; e - Acceptance or rejection of content or file format. 7.1.1.2, 7.1.1.10T0 - Fedora provides no review and acceptance workflow. 1.5 - Fez provides (a), (d), and part of (e). 1.5Fez provides some limited workflow capabilities: manual accept and reject; staging area for submissions; JHOVE invoked to get file format information. Missing from Fez: no notifications; no normalization; no reject bin; no comments on rejection; no submitter-based content validation; no rejection based on JHOVE results; no duplicate and completeness checks.7.1.1.3Reason for rejection - Demonstrate that the system records a set of identifying information or metadata that describes the reason for the rejection of submitted content. Demonstrate two cases: (1) automatic rejection, and (2) rejection by a human reviewer.7.1.1.3T0 - Fedora provides no review and rejection workflow. 1 - Fez provides manual rejection, but no reason for rejection, and no automatic rejection. 17.1.1.4Rejection filter - Demonstrate that the system allows the creation of a filter that can be used to automatically reject submitted content. (This capability will eliminate the need for manual review of some submissions and resubmissions.)7.1.1.4T0 - Fedora has no review / rejection workflow or rejection filter. 0 - Fez provides no rejection filter.07.1.1.5Rejection notification - Demonstrate that the system can notify the producer or donor when submitted content is rejected. Demonstrate two cases: (1) notification after immediate rejection by an automated process, and (2) notification after rejection by manual review.7.1.1.5, 7.1.1.11T0 - no review / rejection workflow or rejection notification. 0 - no rejection notification0(7.1.1.8)Metadata types - Demonstrate that the system can ingest content with associated metadata in the following formats: all NLM DTDs, Dublin Core, MARC21, MARCXML, ONIX, MODS, EAD, TEI, PREMIS, METS. (NOTE: This test is covered by tests 8.1.1, 8.1.8, and 8.1.9)7.1.1.8, 8.1.1, 8.1.8, 8.1.9M/TM=2.75, T=3M=2.75,T=2M=2.75, T=3Takes schemas very well but not necessarily DTDs. Needs disseminators to be configured.7.1.1.10Format conversion - Demonstrate that the system has the capability to convert the format of a file being ingested to a desired supported format. As a test case, demonstrate that a WAV file can be converted to MP3 format when it is ingested. (An external tool may be needed to perform the conversion. If this is the case, demonstrate that the system can invoke the required external tool.) 7.1.1.10, 7.1.1.2T2 - Fedora disseminators can provide converted files at the time of access. 2 - Fez uses ImageMagik to convert image formats, create thumbnails.2Fedora's ImageManip service can convert images between gif, jpg, tiff, png, and bmp; can also resize, crop, watermark, adjust brightness, convert to grayscale.7.1.1.12Resubmission - Demonstrate that the system can ingest a SIP that is resubmitted after an error in the SIP was detected and corrected. Demonstrate two cases: the resubmission can occur after an error was detected in (1) the content of the SIP, and (2) the metadata of the SIP.7.1.1.12T111SIPs can be resubmitted, but neither Fedora nor Fez has any specific support (e.g. no rollback).7.1.1.14Versions - Demonstrate that the system can store, track, and link multiple versions of a file.7.1.1.14T3 - Every datastream in an object (external file or embedded XML) can have multiple versions, which are stored and linked from the object, and can be individually retrieved.2 - Fez add-on packages ("Version Viewing" and "Versioning of Content" expose the underlying Fedora versioning capability to the Fez UI.37.1.1.15aUnique identifiers - Demonstrate that the system assigns a unique identifier to each object ingested. Demonstrate two cases: (1) a unique identifier assigned to a digital object, which may be comprised of a set of component files, and (2) a unique identifier assigned to each of the component files of a digital object.7.1.1.15a, 7.1.1.15bT3 - Unique identifier for every object, and every datastream (file or metadata) within the object.3 - Fez exposes underlying Fedora unique identifiers.37.1.1.15bRelationships - Demonstrate that the system can represent a parent-child relationship between content items. Demonstrate two cases: (1) an object having multiple components (e.g., a document having multiple pages, each in a separate file), and (2) an object having multiple manifestations (e.g., an image having both TIFF and JPEG files).7.1.1.15bT3 - Relationships stored as RDF in RELS-EXT datastream of every object. RDF Triplestore used for quick search and retrieval of relationships. Extendable ontology of object relationships provided.1 - Limited exposure of Fedora's underlying relationships.37.1.1.16Audit trail - Demonstrate that the system maintains an audit trail of all actions regarding receiving submissions (SIPs).7.1.1.16T2.5 - AUDIT datastream (XML) included in every object's FOXML, records submission events.2 - Fez workflows store submission events in PREMIS datastream.2.57.1.2 Ingest - Quality AssuranceT7.1.2.1Virus checking - By design analysis, confirm that the system performs automatic virus checking on submitted content files. 7.1.2.1T000Virus checking must be performed pre-ingest with external tools.7.1.2.2Transmission errors - Demonstrate that the system uses MD5, CRC, checksums, or some other bit error detection technique to validate that each data file submitted is received into the repository staging area without transmission errors. 7.1.2.2T1 - See note.0 - no transmission error checks1Fedora design allows MD5 or other checksum to be provided in SIP, and Fedora will validate that no transmission error occurs during ingest (score=3). However, this feature inoperative in Fedora 2.2.3 due to code bug (score=1).7.1.2.3Submission validation - Demonstrate that the system verifies the validity of submitted content based on the following criteria: submitter; expected file format; file quality (e.g., actual format of file matches the filename extension, and content of file is well-formed); duplication (e.g., existence of object in the repository); completeness of metadata; completeness of file set (e.g., all expected files are included in the submission).7.1.2.3T01 - Fez invokes JHOVE to check file format, but does not reject if incorrect or bad format found.17.1.2.4QA UI - Demonstrate that the system allows NLM staff to perform manual/visual quality assurance on staged SIPs via a user-friendly interface.7.1.2.4T0227.1.2.5Reaction to QA errors - Demonstrate that the system can react to specified QA errors in two ways: (1) request that the producer correct and resubmit the content, or (2) automatically modify the submission (e.g., converting to a supported format).7.1.2.5T0007.1.2.6File/batch accept/reject - Demonstrate that the system enables NLM staff to accept or reject submitted content (SIPs) at the file or batch level.7.1.2.6T01 - Batch or single file, no email17.1.2.7bError reports - Demonstrate that the system generates error reports for ingest quality assurance problems.7.1.2.7bT000No statistics or error reports7.1.2.8Adjustable level of manual QC - By design analysis, confirm that the system has the ability to adjust the level of manual ingest quality control needed, based on the origin of the file.7.1.2.8T0007.1.2.9Audit trail - Demonstrate that the system maintains an audit trail of all actions regarding ingest quality assurance.7.1.2.9T1117.1.4 Ingest - Generate Descriptive Information / MetadataM7.1.4.1Additional metadata - Demonstrate the entry of additional metadata (e.g. subject headings, names, dates, curatorial descriptive metadata - evaluative information that explains why an object is important, whether it was part of a larger collection (e.g., an exhibit), etc.).7.1.4.1M333Creating disseminators for flat metadata is not too hard it's digging out chunk of the objects that are hard and can cause the system to crash when dealing with terabytes.7.1.4.2Validate metadata - Demonstrate ability to validate specified metadata elements.7.1.4.2M222Can setup required elements7.1.4.4Metadata storage - Demonstrate that metadata is stored in the database in a manner that conforms to repository reformatting and linked to their corresponding objects via an identifier. o Demonstrates that basic descriptive metadata is also stored with the objects (e.g., unique identifier, title and date stored in the TIFF header) so that the objects can still be identified in the event that information in the database is corrupted. o See Appendix D for examples of TIFF header metadata requirements. (Use of external tool probable)7.1.4.4M333Both bullet 1 and 2 are 37.1.4.5Required descriptive elements - Demonstrate the ability to recognize required descriptive elements.7.1.4.5M3337.1.4.7Audit trail - Demonstrate the creation of an audit trail of all actions.7.1.4.7M3337.1.3 Ingest - Generate AIPNote 3P7.1.5 Ingest - Coordinate UpdatesNote 3P7.2.1 Archival Storage - Receive DataNote 3P7.2.2 Archival Storage - Manage Storage HierarchyNote 3P7.2.3 Archival Storage - Replace MediaNote 3P7.2.4 Archival Storage - Error Checking and Disaster RecoveryNote 3P7.2.5 Archival Storage - Provide DataNote 3P7.3.1 Data Management - Administer DatabaseNote 3P7.3.2 Data Management - Administer Perform QueriesNote 3P7.3.3 Data Management - Generate ReportNote 3P7.3.4 Data Management - Receive Database UpdatesNote 3P7.4 AdministrationNote 3PP1 - Generate AIPPP1-1Generate AIP - Demonstrate the generation of AIPs from ingested SIPs that do not need normalization.7.1.3.1, 7.1.3.2, 7.1.3.3, 7.4.1P222Fedora/Fez can generate a FOXML or METS file that contains metadata and links to all datastreams but does not create a physical AIP package. P1-2Generate AIP with normalization - Demonstrate the generation of AIPs from ingested SIPs that need normalization - Transform an unsupported format to an accepted format (See Appendix B).7.1.3.1, 7.1.3.2, 7.1.3.3, 7.4.1P000No normalization.P1-3Derivative files - Demonstrate the generation of AIPs that consist of master files and derivatives.7.1.3.6P31.53Fedora's disseminator can be configured to accept images in the gif, jpg, tiff, png and bmp formats and can also convert images between these formats. Fez can create three jpg derivatives for each ingested image datastream: thumbnail, web-preview and access copy.P1-4Master files - Demonstrate the generation of AIPs that consist of master files only.7.1.3.6P222Fedora assigns a PID to each datastream. Fez uses a prefix (archival, preview or thumbnail) to label each datastream.P1-5Store AIP in archival storage - Demonstrate the ability to transfer AIPs to Archive Storage.7.1.5.1, 7.2.1.1, 7.2.1.2P222P1-6Store metadata in DB - Demonstrate the ability to generate and transfer Descriptive Information (metadata) to Data Management Database. 7.1.5.2, 7.3.4.1P333With Fedora's GSearch, all metadata in the FOXML/METS can be indexed.P1-7Link metadata and objects - Demonstrate the ability to store identification information in the Data Management database and link digital objects in the Archive Storage.7.1.5.4P333P1-8Send confirmation - Demonstrate the ability to automatically send confirmation to ingest and/or receiver when AIP and metadata transfers are completed.7.1.5.1, 7.1.5.3, 7.2.1.3, 7.3.3.3P111Both can provide a confirmation on the screen. The email capability is not available for testing.P1-9Send statistical reports - Demonstrate the ability to automatically send statistical reports to ingest and/or receivers when AIP and metadata transfers are completed.7.1.5.1, 7.1.5.3, 7.2.1.3, 7.3.3.3P011Only Fez has a limited on-screen view of "My Created Items". The email capability is not available for testing.P1-10Send error reports - Demonstrate the ability to automatically send error reports to ingest and/or receivers when AIP and/or metadata transfers fail.7.1.5.1, 7.1.5.3, 7.2.1.3, 7.3.3.3P111Both will display an error message on the screen if the ingest fails but Fedora also records it in the log file. The email capability is not available for testing.P2 - Administer Archival Storage & DatabasePP2-1Monitor transfer integrity - Demonstrate the built-in function to automatically monitor and report if any AIPs and metadata are altered or corrupted during data transfer and media change (refresh or replace).7.2.2.1, 7.2.3.2, 7.2.4.1P303Fedora generates a checksum for every ingested datastream. A pre-generated checksum could be supplied in the ingest process but the validation process seems having bugs (fail any supplied checksum, good or bad).P2-2Check data/referential integrity - Demonstrate the built-in function to perform routine and special referential and data integrity checks (CRC or checksums) on files in the Archive Storage and Data Management Database.7.2.4.2, 7.3.1.1, 7.3.1.2, 7.4.4P202Fedora maintains a checksum for each datastream in the repository but provides no referential integrity check.P2-3Routine configuration for data/referential integrity - Demonstrate the ability to allow for routine configuration.7.2.4.2, 7.3.1.1, 7.3.1.2, 7.4.4P111No referential integrity check.P2-4Disaster recovery - Demonstrate the ability to allow for disaster recovery including data backup, off-site data storage, and data recovery.7.2.4.3P212In Fedora there are three ways to export data: Archive (the exported XML file includes all metadata and Base64-encoded datastreams); Migrate (the exported XML file contains metadata and links to datastreams - for migration of objects from one repository to another); Public Access (similar to Migrate but for use outside the context of a Fedora repository). As long as all the datastreams are backed up, Fedora claims that the FOXML file can be used to rebuild the entire repository. Fez has a very limited export function that can only output the metadata and links to datastreams in spreadsheet/CSV format wrapped in XML. P2-5User views - Demonstrate the ability to allow for customized user views of the contents of the storage (create, maintain, and access).7.3.1.4P222P2-6System CM - Demonstrate the ability to allow for configuration management of the system hardware and software.7.4.2P22.52.5Fedora has a limited admin client but Fez provides a GUI interface for system configuration management.P2-7Database CM - Demonstrate the ability to allow for configuration management of the Data Management Database such as table, schema definitions, etc.7.3.1.3P222P2-8Delete AIPs - Demonstrate the ability to allow the authorized staff to delete AIPs from the repository including: removing the digital object's files and retaining associated metadata, or removing both the files and metadata.7.4.3.4P333Fedora provides a purge function that can physically remove an object from the repository. Fez has a delete function but it only marks an object for delete instead of removing it from the repository. Using Fedora to purge an object that was marked for delete by Fez may not completely remove all associated files/data.P2-9Coordinate AIP removal - Demonstrate the ability to generate an alert and coordinate the removal of an AIP with maintenance of metadata held in other systems.7.4.3.5P000P2-10File migrations - Demonstrate the ability to allow the authorized staff to schedule and perform file migrations or migration on request for batched and individual files by authorized staff.7.4.3.6P000P2-11Request DIPs for update - Demonstrate the ability to allow the authorized staff to request DIPs for file migrations and data updates.7.3.4.1, 7.3.4.2, 7.3.4.3, 7.4.3.1, 7.4.3.2, 7.4.6.2P303Fedora can export metadata and/or datastream (in Base64 encoding). Fez can only export metadata and links to datastreams in spreadsheet/CSV format wrapped in XML but not datastreams.P2-12Re-ingest updated DIPs - Demonstrate the ability to allow the authorized staff to reingest updated DIPs as SIPs.7.4.3.3P202Fedora allows the user to specify changes in the FOXML/METS file for re-ingest but it does not allow the same UID to be reingested. Fez is not capable of re-ingesting its own exported content.P2-13Support query requests - Demonstrate the ability to receive, retrieve, display, and deliver data for query requests from other functions such as Ingest, Access, and Administration.7.3.2.1, 7.3.2.3, 7.4.6.1P222P2-14Query requests from different storage locations - Demonstrate the ability to handle query requests with required data to be sourced from different storage locations.7.3.2.2P323Fedora supports data sourced from local, external (remote in FOXMAL) or redirect (not disseminated). Fez supports data sourced from local or redirect.P2-15Queries against all metadata - Demonstrate the ability to run data queries against all metadata used to manage the repository.7.3.2.4P2.522.5With Fedora GSearch, all metadata captured in the FOXMAL/XML file can be indexed for search. Fez has a built-in function that can be used to manage all searchable keys.P2-16Audit trial - Demonstrate the creation of an audit trail of all actions including who, when, how, what and where for Archive Storage and Data Management Database.7.1.3.4, 7.1.5.6, 7.2.1.4, 7.2.2.3, 7.2.5.2, 7.3.2.5, 7.3.3.7, 7.3.4.6, 7.4.3.7, 7.4.6.4P2.51.52.5Fedora/Fez can record all actions in FOXML.P2-17Generate reports - Demonstrate the ability to receive, generate, display, and deliver management information reports and statistics such as summaries of repository holdings by category, summaries of updates by category, user codes, etc., usage statistics for access to repository holdings, and descriptive information for a specific AIP.7.3.3.1, 7.3.3.2, 7.3.3.5, 7.3.4.4P111Fedora has a limited Repository Reports capability that can be invoked from the REST interface (.../fedora/report). The report lists all objects in the repository of a specified type that have been modified or created in a specified timeframe. Fez also has a limited reporting capability that allows the admin user to view a list of "My Created Items" on the screen.P2-18Schedule reports - Demonstrate the ability to generate reports in an ad-hoc manner, automatically or to be triggered by a calendar or by a specific system event.7.3.3.4P00P2-19Time period for reports - Demonstrate the ability to allow the user to specify a time period or set of time periods for reports and statistics.7.3.3.6P111Fedoras limited Repository Reports capability allows the user to specify a time period for the report, e.g., all objects created or modified in the past 24 hours, 7 days, etc. Fez allows the admin user to specify a before or after date to find items only in "My Created Items".P3 - Generate DIPPP3-1Generate DIP for access requests - Demonstrate the generation of DIPs by putting AIPs and Descriptive Information back together for access requests.7.1.5.5, 7.2.5.1, 7.4.6.2P222Fedora has both REST and SOAP interfaces available in its access API (API-A). A coordinated set of web service calls can be made to retrieve all the metadata and datastreams of an object, which can be combined and displayed to a user. Fez provides similar functions for access requests.P3-2Generate DIP for object maintenance - Demonstrate the generation of DIPs by putting AIPs and Descriptive Information back together for content/metadata update, versions upgrades and format migration by authorized staff.7.4.6.2, 7.4.3P222The Fedora Admin Client enables authorized administrators to edit metadata, import new versions of datastreams, and export entire objects for migration. Command line utilities provide key functions of the management API (API-M) that can be invoked directly or from customized scripts. DIP objects can be exported in FOXML/METS format, and can include all metadata and all datastreams (base64-encoded ) in a single XML file. Fez has a workflow-based export function that allows the admin user to export selected community, collection or record in CSV or spreadsheet format wrapped in XML. The exported XML file contains only metadata and file names of datastreams.7.4.1 Administration - Negotiate Submission AgreementT7.4.1.1Manage submission agreements - Demonstrate that the system manages information regarding submission agreements: that it tracks negotiation status and written submission agreements, and that it maintains schedules. 7.4.1.1T0007.4.1.2Edit submission agreements - Demonstrate that the system allows submission agreements to be edited, based on the access level of the user.7.4.1.2T0007.4.1.5Terms of submission agreements - Demonstrate that the system stores the terms of submission agreements, and uses the terms to monitor, review, and process submissions. 7.4.1.5T0007.4.1.6Audit trail - Demonstrate that the system maintains an audit trail of all actions related to submission agreements.7.4.1.6T0007.4.2 Administration - Manage System ConfigurationT7.4.2.1Monitor repository functionality - Demonstrate that the system monitors the functionality of the entire repository.7.4.2.1T0007.4.2.2System configuration - By design analysis, confirm that the system maintains the integrity of the system configuration.7.4.2.2T0 - Info stored in FOXML objects; some info saved to relational DB2 - Fez utility to manually check site installation configuration2Easy-to-use command-line function that rebuilds Resource Index and relational DB if corruption occurs.7.4.2.3Audits operations - Demonstrate that the system audits system operations, performance, and usage.7.4.2.3T1 - Log file contains errors for sysadmin and programmer. Log files at file level. Audit trail for each object in FOXML.1 - Some limited Fez logs17.4.2.4Data management information - Demonstrate that the system collects and can display system information concerning Data Management.7.4.2.4T0007.4.2.5Operational statistics - Demonstrate that the system collects and can display operational statistics concerning Archival Storage.7.4.2.5T0007.4.3 Administration - Archival Information Update7.4.5 Administration - Audit SubmissionT7.4.5.1Audits - Demonstrate that the system can support an audit procedure to verify that submissions (SIP or AIP) meet specified requirements of the repository. The audit method may be based on sampling, periodic review, or peer review. [See NLM DRD Functional Requirements document, section 7.4.5 for description of audit requirements.] (Also partially covered by 7.2.4.2)7.4.5.1T0007.4.5.2Metadata audit - Demonstrate that the system can audit metadata as part of the audit procedure. 7.4.5.2T0007.4.5.3Audit rejection - Demonstrate that the system can reject components of audited information packages, based on specified audit requirements.7.4.5.3T0007.4.5.4Audit report - Demonstrate that the system can generate an audit report, based on the results of periodic audits of SIPs and AIPs.7.4.5.4T0007.4.5.5Audit trail - Demonstrate that the system maintains an audit trail of all actions regarding the auditing of SIPs and AIPs.7.4.5.5T0007.4.6 Administration - Activate RequestsP7.6.1 Access - Coordinate Access Activities - User AccessA7.6.1.1Manage user permissions - Demonstrate the access controls for multiple permission levels and user privileges.7.6.1.1AUser permissions are controlled via XACML. Custom policies can be created, and policies can be nested logically. The need to hold down ctrl while adding members to groups is a little risky - too easy to deselect members.27.6.1.2Manage user restrictions - Demonstrate multiple levels of access restrictions for NIH employees and general public based on licensing terms, embargo periods, IP range restrictions, workstation access, and other possible legal restrictions. 7.6.1.2, 7.6.1.3AXACML policies can be written to allow or deny access at every level of object aggregation, using IP range, inactive/deleted status of datastreams, etc. Fedora supports LDAP simple user/password out of the box, but other sources can be configured.Access restrictions to communities are granular but not as visible as we would like. AD integration is very attractive.27.6.1.4Manage user settings - Demonstrate access settings allow staff to add or edit descriptive metadata7.6.1.4AXACML policies can be written to allow or deny access at the datastream level. Metadata editing requires the Fedora client.Granular, role-based access to add or edit descriptive metadata. This takes some up-front configuration, but works OK. 17.6.1.7Audit users - Demonstrate access mechanisms can identify individual users and maintain audit log of user actions. 7.6.1.7AEvery change to a datastream can be versioned with audit trail record.Premis event synopsis is viewable in the public view, more detailed log is available.27.6.1.5Perform maintenance tasks - Demonstrate maintenance access including adding new files, manipulating images, editing metadata, performing format conversions/migrations, and troubleshooting system problems.7.6.1.5AFedora allows adding files, and files can be manipulated via disseminators. Some troubleshooting will require the client or command line actions.Fez allows adding new files and editing metadata. Image manipulation and format conversion is not directly supported, but Fez can manage content after it has been externally manipulated or converted. System troubleshooting is excellent, with a very thorough sanity checker to detect common installation problems. Run-time errors are saved to the log and can be optionally sent to the browser, with configurable levels of error detail (time, object, method, parameters).17.6.1.6Manage system rights - Demonstrate ultimate system rights access for NLM system administrators and programmers.7.6.1.6ASome admin access is controlled by database and OS accounts, but Fedora user privileges are controlled via the XACML policies.The ability to add users or change user privileges can be isolated to users with specific application administrative privileges. There is also a Community Administrator role. Rights are stored in the Fez DB.27.6.1 Access - Coordinate Access Activities - Rights/Data Control of ObjectsA7.6.1.8Manage access rights - Demonstrate access rights and conditions to materials and storage directories provide for a combinational of create/write; edit; read; delete privileges.7.6.1.8AGranular access control to objects\datastreams\disseminators or aggregates\repository-wide policies via XACML. Custom policies can be created, and policies can be nested logically.Editing security options at the community, collection and item level appears intuitive and powerful, but we have been unable to successfully test most of this area.27.6.1.9Manage metadata rights - Demonstrate access rights may be associated with the metadata relating to an individual object 7.6.1.9AGranular access control to objects\datastreams\disseminators, including metadata datastreams, via XACML policies.Access to the object's record should be controllable. Unable to test this successfully with granular permissions.27.6.1.13Manage relationships - Demonstrate access rights and conditions can be inherited from a parent object to any child object. 7.6.1.13AXACML policies can utilize the RELS-EXT values to allow or deny access.Security settings allow for parent-child propagation of security values.27.6.1.14Manage relationships - Demonstrate access rights and conditions can be assigned to an object on an individual or group basis at same time.7.6.1.14AXACML policies can be assigned to a content model or by PID.Child objects can inherit parent access controls or have their own independent controls. As with 7.6.1.8, this has not been successfully tested.17.6.1.16Automated retrieval - Demonstrate objects in the repository are accessible for data mining or automated retrieval.7.6.1.16AAutomated retrieval is not facilitated, but comprehensive indexing of metadata and fulltext is available with indexing plug-in.Automated retrieval is not facilitated, but comprehensive indexing of metadata and fulltext is available with indexing plug-in.17.6.1.17Metadata access - Demonstrate access to deleted and retracted metadata is retained.7.6.1.17AFedora supports write-once, where any changes to datastreams are versioned.Versioning of underlying datastreams is delegated to Fedora. Metadata, attached files and hyperlinks can be versioned through Fez.17.6.1.18Metadata harvesting - Demonstrate metadata harvesting following the OAI-PMH guidelines. 7.6.1.18AFedora includes an OAI provider to expose content for harvesting. Recently rewritten for Fedora 3.0.Fez can utilize the Fedora OAI provider.17.6.1.10Access rights - Demonstrate access rights and conditions of use are applied to each digital object and its related metadata and are machine readable and actionable. 7.6.1.10, 7.6.1.11AXACML policies are machine-readable by design.Rights can be applied per datastream, object and higher-level aggregations.27.6.1.12Access conditions - Demonstrate access conditions are specific to a digital object.7.6.1.12APolicies can be applied at the datastream level and all higher aggregations of content.Rights can be applied per datastream, object and higher-level aggregations.27.6.1.15Free/Restricted access - Demonstrate free (items available via internal/external delivery mechanisms) and restricted access (access permission must be satisfy various criteria) status for objects, files, metadata, etc.7.6.1.15AXACML policies can be written to allow or deny access at every level of object aggregation, using IP range, inactive/deleted status of datastreams, etc. Policies should be able to accommodate embargo logic ("moving wall").Access controls are granular (in theory, unable to test successfully). No "embargo" logic is present. 27.6.1 Access - Coordinate Access Activities - Search and RetrievalA7.6.1.19508 compliance - Demonstrate the search interface is web-accessible and Section 508 compliant.7.6.1.19AFedora's thick client does not appear to be Section 508 compliant. However, NLM staff could use alternative methods for ingesting and managing content such as running UNIX commands or via a Web UI. Section 508 compliance is a design goal in any upcoming UI development. Fez is an Australian product, so it is not bound by the Section 508 requirements. Since the product is open-source, NLM could easily tweak the HTML templates, etc. to create accessible UIs, etc. were feasible.1.57.6.1.20Search features - Demonstrate search includes: metadata, full-text, standard boolean, proximity, "more like" this"7.6.1.20, 7.6.1.21, 7.6.1.22, 7.6.1.23, 7.6.1.24AMetadata searching with some operators, less GUI than Fez. GSearch supports full text indexing and searching, proximity.No explicit "or" searching in our environment, but UQ has it. Lots of metadata searching, with wildcards. No proximity or "more like".17.6.1.25Search results display - Demonstrate search results display includes date sort; relevancy ranking; alpha by author or source. 7.6.1.25Ano custom ordering of results. Default order is by PID.No Author or source, but date, relevance, title, description.27.6.1.26Relevancy ranking - Demonstrate whether relevancy ranking can be manipulated via system as well as user defined settings. 7.6.1.26An/aNot accessible through admin interface.07.6.1.29Federated search - Demonstrate federated searching of different repository sites.7.6.1.29ACan search across all or select communities/collections via advanced search.27.6.1.30Advanced search - Demonstrate advanced search includes search history; saved searches; saved citation lists/bibliographies; alerts; various functions and formats; dynamic selection of delivery media without recreating search query.7.6.1.30Anone of these functions are presentCan save searches as RSS feeds, 17.6.1.31Display formats - Demonstrate a variety of standard display formats are provided and whether they are customizable by user7.6.1.31AFedora lets you select the fields to display.Can be saved as XML, RSS, citation-only. Not customizable by user.17.6.1.32Alternate search interfaces - Demonstrate availability of alternate search interfaces for mechanisms such as handhelds and PDAs.7.6.1.32A07.6.1.33Object access - Demonstrate access to the appropriate copy of the identified item (text, image, video, etc.) 7.6.1.33ADatastreams have no preference.Unclear how to identify the appropriate datastream, although one is highlighted. Can identify differences in datastream descriptions.07.6.1.34Library holdings - Demonstrate integration of search results with library holdings.7.6.1.34A07.6.1.35Response time - Demonstrate acceptable response time. 7.6.1.35AResponse time is acceptable, within our test environment and limited collection.Response time is acceptable, within our test environment and limited collection.17.6.1.36External search engines - Demonstrate searching by outside search engines such as usa.gov, Google, and Yahoo. 7.6.1.36Aso far, evidence suggests only library web pages with a "browse view" external to Fedora are spidered.uq.edu's espace browse pages appear to be indexed by Google17.6.1.37External system access - Demonstrate external access to other repositories or systems performing web harvesting functions.7.6.1.37AFedora has a built-in OAI-PMH Provider Interface, and all objects have a compliant DC record. Only the DC metadata may be disseminated, however.Fez could delegate the OAI-PMH service to Fedora.17.6.1.38Language support - Demonstrate how multiple languages and non-Roman scripts are supported in search, retrieval and display. 7.6.1.38AChinese characters do not display in test record (fedorans:137).Chinese characters displayed in search results (fedorans:137), but not searchable.17.6.1.39Versioning - Demonstrate access to all versions of digital objects in the repository is provided. 7.6.1.39AFedora objects can be versioned at every level, including disseminators.All versions are accessible, but no versioning functionality for uploaded content. This is in the works for a future release. 27.6.1.40Search settings - Demonstrate system settings and user-defined settings in the search functions are provided. 7.6.1.40AOnly default system-provided search settings are offered.Only default system-provided search settings are offered.17.6.2 Access - Generate DIPA7.6.2.1Integrate holdings - Demonstrate integration of search results with library holdings.7.6.2.1ANo functionality built-in to Fedora for this.No functionality built-in to Fez for this.07.6.2.2Retrieval and notification - Demonstrate the generation function accepts a dissemination request, retrieves AIP from archival storage and moves a copy of the data to a staging area for further processing, and creates and sends a report request to data management to obtain appropriate metadata. 7.6.2.2, 7.6.2.3, 7.6.2.4AAIP/DIP is conceptual, but the search API can result in a list of any and all datastreams, including all metadata associated with the object.AIP/DIP is conceptual. Search interface can provide links to multiple derivatives of an object, the archival master and associated metadata.27.6.2.7Audit trail - Demonstrate an audit trail of all actions is created and stored. 7.6.2.7ATomcat logs can provide dissemination requests (according to Indiana Univ. DLP).Fez can track downloads per file, but this is not working in testing.17.6.2.5Response and delivery - Demonstrate that the prepared DIP response is placed in the staging area and a message is generated and sent to Coordinate Access Activities that the DIP is ready for delivery. 7.6.2.5AThis aspect of OAIS is not currently modeled by Fedora. Fedora does not appear to use a staging area but serves requested content directly from the repository.This aspect of OAIS is not currently modeled by Fez. Fez does not appear to use a staging area but serves requested content directly from the repository.07.6.2.6Storage retrieval - Demonstrate that Generate function accesses data objects in staging storage and applies the requested processes if special processing is required.7.6.2.6ANo staging storage area per se, but disseminators can process the master file(s), separating it from the DIP.No staging storage area per se, and Fez architecture inhibits the disseminator functionality of Fedora.1Disseminator layer of Fedora is quite powerful and flexible, but cumbersome to configure in 2.2.3. Fez's inability to leverage the Fedora disseminators is a big downside.7.6.3 Access - Deliver ResponseA7.6.3.1Web-accessibility - Demonstrate the display interface is web-accessible. 7.6.3.1AFedora has a fairly limited web interface for retrieval.Fez is entirely web-accessible.27.6.3.2Downloading - Demonstrate export function that provides XML output for batch downloads7.6.3.2AObjects can be exported as METS packages, and some individual datastreams are downloadable as XML.Fez can export some (but not all) metadata into XML. It cannot then re-ingest from the export output. Export is intended for spreadsheet manipulation of metadata.17.6.3.3Saving content - Demonstrate users are allowed to save digital content to a hard-drive, e-mail, and/or save search results. 7.6.3.3AFiles may be downloaded. There does not appear to be a function for emailing or saving search results.Files may be downloaded. There does not appear to be a function for emailing or saving search results.17.6.3.5System notification - Demonstrate a confirmation message is returned to the Coordinate Access Activities section after response has been sent.7.6.3.5AThis aspect of OAIS is not currently modeled by Fedora. This aspect of OAIS is not currently modeled by Fez. 07.6.3.6Audit trail - Demonstrate an audit trail of all actions is created and stored.7.6.3.6ATomcat logs can provide dissemination requests (according to Indiana Univ. DLP).Fez can track downloads per file, but this is not working in testing.17.6.3.4Response request - Demonstrate a response request is received from Coordinate Access Activities 7.6.3.4ADemonstrated retrieval of objects via the UI without issue.Demonstrated retrieval of objects via the UI without issue.28.1 Metadata RequirementsM8.1.1Metadata formats - Demonstrate that the system can accept metadata associated with objects in at least the following formats: All NLM DTDs, Dublin Core, MARC21, MARCXML, ONIX, MODS, EAD, TEI. 8.1.1M/TT=3 M=3T=3 Any metadata could be added as a datastream; M=3.T=3 M=3Fedora is completely agnostic about what kinds of metadata and number of metadata objects that can be assigned to any object8.1.2Metadata checks - Demonstrate the built-in checks on the incoming metadata. Records not containing the minimally defined set of fields should be flagged as problems, either to be returned to the submitter, or sent locally for metadata enhancement. 8.1.2M333Fedora would need an additional tool to perform checks.8.1.5Metadata updates - Demonstrate the ability to allow for metadata updates. 8.1.5M32.53Fedora client only has one template field for descriptive title; actual object metadata box can take anything just need disseminator to do something with it.8.1.6aMetadata search and display - Demonstrate the ability to search and display metadata (use of external tool possible). 8.1.6aM32.538.1.8PREMIS - Demonstrate standards compliance for PREMIS (use of external tool possible). 8.1.8M/TT=3 M=3T=2 Fez limited. Fez won't display Premis metadata if it was added in Fedora. M=2T=3 M=3Fez creates PREMIS metadata for each object, stored as Fedora datastream in the object.8.1.9METS - Demonstrate standards compliance for METS (use of external tool possible). 8.1.9M/TT=3 Fedora can ingest METS SIPs, and export objects in METS format. M=3T=1 Fez limited. METS could be stored as a datastream. M=2T=3 M=3Fedora can store METS metadata as a datastream in an object, e.g. to drive a METS-based page-turner. App ADescriptive metadata - Demonstrate that the minimum descriptive metadata requirements described in Appendix A are accepted. App AM3239.1 Additional Technical Infrastructure RequirementsT9.1.1OAI-PMH - Demonstrate that the system can respond to OAI-PMH requests as a data provider. 9.1.1T202Fedora has a basic OAI-PMH capability, and an extended capability using the optional OAI-Provider tool (in the Fedora Service Framework).9.1.2Z39.50 - By design analysis, confirm that the system can respond to data requests using the Z39.50 standard.9.1.2T0009.1.3SRU/SRW - By design analysis, confirm that the system can respond to data requests using the SRU and SRW data access standards.9.1.3T000VTLS provides SRU/SRW for Arrow project.9.1.4SOAP - Demonstrate that the system can respond to web service requests using SOAP. 9.1.4T3039.1.5UNICODE - Demonstrate that the system supports UNICODE.9.1.5T323UNICODE filename not displayed properly in Fez. UNICODE file content handled ok.9.1.6OpenURL - By design analysis, confirm that the system is compliant with OpenURL.9.1.6T0009.1.7Z39.87 - By design analysis, confirm that the system supports the Z39.87 image metadata standard.9.1.7T000Notes:1. Subgroups: A=Access, M=Metadata, P=Preservation, T=Technical Infrastructure2. Score indicates the extent to which the test element could be demonstrated: 0=None, 1=Low, 2=Moderate, 3=High3. Preservation tests - These sections of the functional requirements are covered by Test Plan sections P1, P2, and P3, which were defined by the Preservation subgroup to facilitate testing.4. Test elements having blue background are the subject of outstanding questions from the Access subgroup.      PAGE \* MERGEFORMAT 71 .=HRSTWY\lԹ㵭tibWbWOjhUjh]/h/ U h]/h]/hF~bh]/B*phhF~bh]/B*OJQJph%hR@5B*CJOJQJ\aJph6_h`nh%cJCJ PJaJ h%cJCJ PJaJ h%cJCJ aJ hR@hR@hR@CJHOJQJaJHhF~bCJHOJQJaJHhbuhR@CJHOJQJaJH hDA0hR@hR@;OJQJhbuhR@;OJQJTUVbDkdD$$IfTl$ t6O44 laT *$$Ifa$gdF~bDkd$$IfTl@ $ t644 laT *$$Ifa$VWXYZ[\l@ T * - $ )(gd:wgd%cJDkd$$IfTlh$ t644 laT   : ; < = > ? @ A _ `   2 3 4 N ۺ̬ۉ̬w̬#jh/ UmHnHu#jch/ UmHnHu!hdGCJOJQJaJmHnHujhUmHnHu#jh/ UmHnHujh/ UmHnHuhdGmHnHuh))-hdG0JmHnHujhUh-N O P Q R S T U s t  $ % & ' ( ) * + I J y z { ŴӈŴvŴ#jWh/ UmHnHu#jh/ UmHnHuh))-hdG0JmHnHuhjhU!hdGCJOJQJaJmHnHujhUmHnHuhdGmHnHujh/ UmHnHu#j]h/ UmHnHu'    . / Z [ \ v w x y z { | } ŴӈŴvŴ#jh/ UmHnHu#jQh/ UmHnHuh))-hdG0JmHnHuhjhU!hdGCJOJQJaJmHnHujhUmHnHuhdGmHnHujh/ UmHnHu#jh/ UmHnHu'  | F ?g5$dz'9gd7gd:w)- $    $ % & @ A B C D E F G e f x y z ŴӈŴvŴ#jEh/ UmHnHu#jh/ UmHnHuh))-hdG0JmHnHuhjhU!hdGCJOJQJaJmHnHujhUmHnHuhdGmHnHujh/ UmHnHu#jKh/ UmHnHu':;]^_yz{}~8ŴӈŴvŴ#jh/ UmHnHu#j?h/ UmHnHuh))-hdG0JmHnHuhjhU!hdGCJOJQJaJmHnHujhUmHnHuhdGmHnHujh/ UmHnHu#jh/ UmHnHu'89:<=>?@^_DEF`abdeŴ}ogcgQ#j3 h/ UmHnHuhjhUjhUmHnHu#jh/ UmHnHuhd0JmHnHuh))-hdG0JmHnHuhjhU!hdGCJOJQJaJmHnHujhUmHnHuhdGmHnHujh/ UmHnHu#j9h/ UmHnHuefgh./023456TUxyzǼǼǼw#j h/ UmHnHu#j- h/ UmHnHu#j h/ UmHnHujh/ UmHnHuhdGmHnHuh))-hdG0JmHnHuhjhU!hdGCJOJQJaJmHnHujhUmHnHu)#$efpcd4hi yļ̴̡̩̩̩̩{skcch'*%OJQJh/OJQJhGOJQJhOJQJh/#fh/#fOJQJhOJQJhhOJQJh#'sOJQJhwQh mOJQJhmDOJQJh6OJQJh"jOJQJhwQhCWOJQJ hF(h m h:whCW hF(hCWh]/jh]/h/ CJUaJ%yzz'9"""%"1":"K"P"S"T"c"m"y"""""""""""""#####(#/#o$$c%{%%%%y&~h^5OJQJ\hwQhJX5OJQJ\h"jOJQJhWPOJQJhf9OJQJhwQhJXOJQJ hwQhJX h:whJX hwQh[hwQh[OJQJhOJQJhhOJQJhwQhCWOJQJh/#fOJQJ19Y #o$c%{%%y&@(***;+=+|+++,-.[..//1gd*gd* & Fdd[$\$gdJXgd:wgd gd7gdJXy&&@(M(****:+;+=+h+i+|+++,%,[..///0033k4x4444444444555 5c5d55555555羸ܱh5DhY(;hrhh*h*B*OJQJphh6&OJQJh*h*OJQJ h*h* h PJhwQhJXPJ hwQhJX hF(hJX hwQh[hwQh[OJQJhwQhJXOJQJhwQhJX5OJQJ\213k4x4444445 5r55555666=66 & F2dd[$\$gd* & F1dd[$\$gd* & F1dd[$\$gd* & F0dd[$\$gd* & F0dd[$\$gd*gd*gd*566/6465666=677b777777 88"8#888#9$9a9b9m99999999::;;';6;7;G;f;g;;;;;;<3<R<h<~<<<<$=%=w=x=|=======>'>(>)>4>>>>??8?W?X?????h]l^h#'sh2Eh*h*B*OJQJph h*h*hY(;hrT667#7<777 88889%9c99999:: & F4dd[$\$gd* & F3dd[$\$gd* & F3dd[$\$gd*gd* & F2dd[$\$gd* & F2dd[$\$gd*::;8;@;h;;;~<<<<&=y====)>4> & F6dd[$\$gd* & F6dd[$\$gd* & F5dd[$\$gd*gd* & F4dd[$\$gd* & F4dd[$\$gd*4>>>?Y????@c@@`AAAAAAABsBBB & F8dd[$\$gd* & F8dd[$\$gd*gd* & F7dd[$\$gd* & F7dd[$\$gd*?????B@a@b@@@@UA^A_AoAAAAAAAAAAABBRBqBrBBBBBBCCC D D8DqE9FXFF+G,GGGGGGG/I;Iÿæώh OJQJjh0JOJQJU*h4Qh*0JOJQJ*j' hUhjhUhzh*h*OJQJhj,h*h*B*OJQJphhrh* h*h*hY(;6BCCCC D8DLEqEEEfFFHJJJMPMsMtMgd'2gd7gd'2gd:w & F:dd[$\$gd*gd*gd* & F9dd[$\$gd* & F9dd[$\$gd*;IVI{IIIIJRJJJJJOMPMrMsMtMMMMMMMMMMM N NN&N5N6N;N*OJQJ\hwQhJX5OJQJ\.$PFPPPQQQQQNRShSS?T}TTTUfUUUV & Fdd[$\$gdJX & Fdd[$\$gdJXgdJXdd[$\$^gd2 & Fdd[$\$gdJXVLVVVVVW_?_7cPcQcff&f'f4f@fAf-gNggggggggj j!j"j2jjjļ̵̽||h4Q5OJQJ\ hZPJh'2h'25OJQJh'2h'25OJQJ\h'2hJX5OJQJ\h6&OJQJh5thJX5>*OJQJ\hwQhJX5OJQJ\ h%+~PJhwQhJXPJhwQhJX5PJ\hwQhJXOJQJ0_`7aabc7cQccPdyeefAfff'gUggg`h~hh & F dd[$\$gdJX & F dd[$\$gdJX & F dd[$\$gdJXgdJX & Fdd[$\$gdJXhj"jjlo!pqqr1rrrsGss2ttuyuvv & Fdd[$\$gdJXgd  & F dd[$\$gdJX & F dd[$\$gdJXgdJX & F dd[$\$gdJXlmnmommmmmoo!p)pupvpqqqqqqrrss(sGsssvvvXyYy{{|||||}}~뼱뼢뼱뼆xlh'2h'25OJQJh'2h'25OJQJ\h'2hJX5OJQJ\ h PJh6&OJQJh5thJX5>*OJQJ\hwQhJXOJQJhwQhJX5OJQJ\ hGPJhGhJXPJ hzPJ hO_>PJ hcPJhwQhJXPJhwQhJX5PJ\*vx|y+z{{|}*}h}}}}S~u~ pv0t & Fdd[$\$gdJX & Fdd[$\$gdJXgdJX & Fdd[$\$gdJX~~ !"/op7IghvCIڈ5Z[UXqsǗʾ񰥙{t hF(h|hwQh[PJ h_LCPJh_LChJXPJ hiRPJhwQhJX5PJ\hwQhJXOJQJhwQhJX5OJQJ\h'2h'25OJQJh'2h'25OJQJ\h'2hJX5OJQJ\h4Q5OJQJ\hwQhJXPJ htGPJ*tIhCڈs ,OǗgd7gd:wgd[ & Fdd[$\$gdJX & Fdd[$\$gdJXgdJX & Fdd[$\$gdJXǗ-5MJ[;է#*+2P#4!?s¼±œztztzhzhzhzzbz hI4PJhwQh5PJ\ hR PJhwQhPJhwQh5OJQJ\hwQhOJQJ hwQhhwQh|5OJQJ\h25OJQJ\ h(PJhwQh|PJ$hYVh|5B*OJPJQJphh6OJQJh.OJQJhwQh|OJQJ hwQh|"w8ǠF; & Fdd[$\$gd|gd  & Fdd[$\$gd| & Fdd[$\$gd|gd|gd| WէM2#4?sgd[Q & Fdd[$\$gd & Fdd[$\$gd & Fdd[$\$gdgd gdgd7 & Fdd[$\$gd|sծٮ=޲ %γٳȴɴʹKMRhǺԺfhǼyqmhjhUhwQhac5OJQJ\hwQhacOJQJ hwQhac hPJ hIPJ h1=PJh1=hPJh1=OJQJhwQhOJQJ hwQh h.PJhwQh5OJQJ\ hRFPJ hPJhwQhPJh[QhPJ'$ڭ =ױ γٳɴ & Fdd[$\$gd1=gdgd7 & Fdd[$\$gdgd  & Fdd[$\$gdgdq" & Fdd[$\$gdAD۸KǺԺf1gdacgd7 & Fdd[$\$gdgd  & Fdd[$\$gd & Fdd[$\$gd & Fdd[$\$gdvXY`al23~GHIdeøêââê잓΋잀uêjhUjhUh6OJQJjhUhh_OJQJhwQhac5OJQJ\hwQh h7OJQJhwQhacOJQJjh0JOJQJU*hwQhac0JOJQJ*jhUjhU)l@rt+.6c & F"gd;o & F(gd;o & F gd;o P Hgd;o & F'gd;ogd;o f!gd;o$a$gd;ogd:wgd gdac?@qr+6RKN(üwogbo^WWo hm,h;oh]\ h;o6h=7h;o6hm,h;o5h`gJh;o6 h;o5h;o#h`h;o5CJOJQJ^JaJh;o5CJOJQJ^JaJh,t_ h/ph/ph/phs~ h,t_h,t_hwQhacOJQJjh0JOJQJU*hwQhac0JOJQJ*jhUjhU"Ou"%R & F+gd;o & F+gd;o & F)gd;o & F%gd;o & F$gd;o & F gd;o & F!gd;o & F.gd;ogd;o P Hgd;o & F"gd;o(1s'(Ctu!"4 %01QRb. .QGRSt0;<]ÿ÷hdph;o5 hZh;oh9E8h;o5h` h=h;oh=h;o5h? gd;o & F-gd;ogd;o & F,gd;o & F&gd;o & F/gd;o & F*gd;o & F gd;o & F+7$8$H$gd;o & F+gd;o & F+gd;o] ;GRh xy} !#01=>?PwxĽg4jhDA0h/ 5CJOJQJU^JaJmH sH +hDA0ho{5CJOJQJ^JaJmH sH #hCWho{5CJOJQJ^JaJho{5CJOJQJ^JaJh/p hehehehs~h.1ihm,h;o5hYh;o5h9E8h;o5 hm,h;oh;o hQ h;o h;o5(?PYanwx7BHbhix $Ifgd[QFfR$d7$Ifa$gd[Q d7$Ifgd[QgdCWgd:w & F# ^gd;o gd;ohix<μvrnjrhg`hs~ho{ho{CJOJQJ^J hDA0hhCJOJQJ^JaJ hDA0h`CJOJQJ^JaJ hDA0ho{CJOJQJ^JaJ hDA0ho{#hDA0ho{5CJOJQJ^JaJ4jhDA0h/ 5CJOJQJU^JaJmH sH +hDA0ho{5CJOJQJ^JaJmH sH (ADkdZ$$Ifd4֞Z l#*4`FT p b444 daf4yto{ $Ifgd[Q} $Ifgd[Q d7$Ifgd` d7$Ifgd[Q |M@@777 $Ifgd[Q d7$Ifgd[Qkd*$$Ifd4֞Z l#*4 FT p b444 daf4yto{<D7 d7$Ifgd[Qkd$$Ifd4֞Z l#*4 F T    p    b444 daf4yto{ $Ifgd[Q<COrX $Ifgd[Q d7$Ifgd[Q >M@@777 $Ifgd[Q d7$Ifgd[Qkd$$Ifd4֞Z l#*4`F T   p   b444 daf4yto{zt $Ifgd[Q/QM@@777 $Ifgd[Q d7$Ifgd[Qkd$$Ifd4֞Z l#*4 FT p b444 daf4yto{QD77 d7$Ifgd[Qkd$$Ifd4֞Z l#*4 F T    p    b444 daf4yto{ $Ifgd[Q^_Dkdd$$Ifd4֞Z l#*4`F T   p   b444 daf4yto{ $Ifgd[QWX $Ifgd[Q d7$Ifgd[QM@3* $Ifgd[Q d7$Ifgdh d7$Ifgd[QkdB$$Ifd4֞Z l#*4 FT p b444 daf4yto{D7 d7$Ifgd[Qkd $$Ifd4֞Z l#*4 FT p b444 daf4yto{ $Ifgd[Q ^_ $Ifgd[Q d7$Ifgd[QMHCC2$$7$8$H$Ifa$gd gd:w gdo{kd $$Ifd4֞Z l#*4 FT p b444 daf4yto{Tt %2<WYOPXhOQUV^t~./8ⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭⴭ hDA0h -h h B*CJOJPJQJ^JaJph-hz25B*CJOJPJQJ\^JaJph3h h 5B*CJOJPJQJ\^JaJphheD38>IUkd!$$IflKr@""}24>[%b444 layt  $7$8$H$Ifgd $$7$8$H$Ifa$gd  $$7$8$H$Ifa$gd N@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd"$$Iflw֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd kd#$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt  GXY$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  %+N@@@@@@ $7$8$H$Ifgd kd$$$Ifl ֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd } N@@@@@@ $7$8$H$Ifgd kd%$$Ifl֞@Q""N-}24>, /%b444 layt  CDNWY$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd&$$IflZ֞@Q""N-}24>, /%b444 layt LNO$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd OPXGOQN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd'$$Ifl ֞@Q""N-}24>, /%b444 layt QRTUV,kd_($$Iflw֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd V^ku~$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd~v $7$8$H$Ifgd  N@@@@@@ $7$8$H$Ifgd kd;)$$IflW֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd wN@@@@ $7$8$H$Ifgd kd*$$Ifl`֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd*$$IflW֞@Q""N-}24>, /%b444 layt +-.$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ./8N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd+$$Ifl ֞@Q""N-}24>, /%b444 layt 8@%'pqbcdn{` a j u   $ % F G I L M U c     ' :       Z]`ain# ST\t?@IVγ'h~vB*CJOJPJQJ^JaJph hDA0h -h h B*CJOJPJQJ^JaJph3h h 5B*CJOJPJQJ\^JaJphF$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd %N@@@@ $7$8$H$Ifgd kd,$$Ifl֞@Q""N-}24>, /%b444 layt %'vw`bc$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd cdnN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd-$$Ifl ֞@Q""N-}24>, /%b444 layt 2 [ _ ` $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ` a j    N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdc.$$Ifl֞@Q""N-}24>, /%b444 layt  ! # $ $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd $ % F G N@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd?/$$Ifl֞@Q""N-}24>, /%b444 layt G I J K L $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd L M kd0$$Ifl?ֈ@""N-}24>, /% <b444 lap<yt M U       $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd   '    N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdL1$$Ifl֞@Q""N-}24>, /%b444 layt     $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd    RZ\N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd(2$$Ifl0֞@Q""N-}24>, /%b444 layt \]_`a,kd3$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd ai$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  N@2@ $7$8$H$Ifgdn $7$8$H$Ifgd kd3$$Ifl֞@Q""N-}24>, /%b444 layt  ;PRS$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd ST\N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd4$$Ifl֞@Q""N-}24>, /%b444 layt :>?$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ?@IN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd5$$Ifl֞@Q""N-}24>, /%b444 layt !SU=>@CDL_hj{| 56>[GIMNjqsvw ?FHKL hDA0h -h h B*CJOJPJQJ^JaJph3h h 5B*CJOJPJQJ\^JaJphN$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdt6$$Iflc֞@Q""N-}24>, /%b444 layt ,kdP7$$Iflw֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd KSU$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd =>N@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd,8$$Ifl֞@Q""N-}24>, /%b444 layt >@ABC$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd CDkd9$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt DL`hjxz{$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd {|N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd9:$$IflH֞@Q""N-}24>, /%b444 layt ,kd;$$Ifl3֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  245$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  56>N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd;$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ?GIN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd<$$Ifl֞@Q""N-}24>, /%b444 layt IJLMN,kdG=$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd Njqstuv$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd vwkd>$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt w$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd kdF?$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd kdi@$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt  $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd kdA$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt ?FHIJK$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd KLkdB$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt L$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd 6=?BCkrtwx}jl,.56;G " ) * / D       !!!3h h 5B*CJOJPJQJ\^JaJph hDA0h -h h B*CJOJPJQJ^JaJphNkdC$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd kdD$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd kdF$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt 6=?@AB$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd BCkd;G$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt Ckrtuvw$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd wxkd^H$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt x$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd kdI$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd kdJ$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd kdK$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt Ycmw}$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  FPZdjN@@@@@@ $7$8$H$Ifgd kdM$$IflH֞@Q""N-}24>, /%b444 layt jl$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd $,.N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdM$$IflH֞@Q""N-}24>, /%b444 layt .245$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd 56;N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdN$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd     N@@@@@ $7$8$H$Ifgd kdTO$$Ifl֞@Q""N-}24>, /%b444 layt  " & ( ) $$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd ) * /    N@@@@ $7$8$H$Ifgd kdP$$Iflw֞@Q""N-}24>, /%b444 layt      $$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd    !!!N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdP$$Ifl֞@Q""N-}24>, /%b444 layt !!!!$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd !!!1":"C"M"U"N@@@@@@ $7$8$H$Ifgd kdQ$$Ifl֞@Q""N-}24>, /%b444 layt !!!!U"W"W#X#]#u#($*$$$$$u%w%%%%%%&&& &&&(( (*( ) ) )))))J*L*e*f*k*|**+8+9+>+H+++++++f,h,o,p,u,,---- -+- . .ȴ'h CB*CJOJPJQJ^JaJph3h h 5B*CJOJPJQJ\^JaJph-h h B*CJOJPJQJ^JaJph hDA0h GU"W"T#V#W#$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd W#X#]#$ $$ $($N@@@@@@ $7$8$H$Ifgd kdTR$$Ifl֞@Q""N-}24>, /%b444 layt ($*$$$$$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd $$$Q%Z%c%m%u%N@@@@@@ $7$8$H$Ifgd kdS$$IflH֞@Q""N-}24>, /%b444 layt u%w%%%%$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd %%%%N@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdS$$IflH֞@Q""N-}24>, /%b444 layt %%%%&$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd &&kdT$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt &&&&&&&((($$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  (( (((() )N@@@@@@ $7$8$H$Ifgd kdU$$Ifl֞@Q""N-}24>, /%b444 layt  ) ))))$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd )))&*0*:*D*J*N@@@@@@ $7$8$H$Ifgd kdV$$Ifl֞@Q""N-}24>, /%b444 layt J*L*b*d*e*$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd e*f*k***+N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdaW$$IflH֞@Q""N-}24>, /%b444 layt +5+7+8+$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd 8+9+>++++N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd!X$$Ifl֞@Q""N-}24>, /%b444 layt ++++$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd +++`,f,h,N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdX$$Ifl֞@Q""N-}24>, /%b444 layt h,l,n,o,$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd o,p,u, ---N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdY$$Ifl֞@Q""N-}24>, /%b444 layt ----$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd -- -. . .N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdaZ$$Ifl֞@Q""N-}24>, /%b444 layt  ....$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  ..../.......//////d0f00000V1X1111 2222223333333R4T4[4\4b4m4p4_5a5d5譖-h h B*CJOJPJQJ^JaJph3h h 5B*CJOJPJQJ\^JaJph3h h 5B*CJOJPJQJ\^JaJph hDA0h -h h B*CJOJPJQJ^JaJph2......N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd![$$Iflw֞@Q""N-}24>, /%b444 layt ....$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ...///N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd[$$Iflw֞@Q""N-}24>, /%b444 layt ////$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ///*030=0G0Q0N@@@@@@ $7$8$H$Ifgd kd\$$Iflw֞@Q""N-}24>, /%b444 layt Q0\0d0f0000$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd 000N1V1X1N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kda]$$Ifl֞@Q""N-}24>, /%b444 layt X1111$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd 1112222N@@@@@ $7$8$H$Ifgd kd!^$$Ifl֞@Q""N-}24>, /%b444 layt 22222$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd 222y333N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd^$$Iflw֞@Q""N-}24>, /%b444 layt 3333$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd 333J4R4T4N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd_$$Iflw֞@Q""N-}24>, /%b444 layt T4X4Z4[4$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd [4\4b45_5a5N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kda`$$Ifl֞@Q""N-}24>, /%b444 layt d5n5555587:7;;;;;<=<==>>>>> ? ????"?#?(?H?????? @@@@@AAAAA$A@ABB B BBѰіѰіііʖіііііʖііі'hHB*CJOJPJQJ^JaJph3h h 5B*CJOJPJQJ\^JaJph3h h 5B*CJOJPJQJ\^JaJph hDA0h -h h B*CJOJPJQJ^JaJph-h h CB*CJOJPJQJ^JaJph3a5555$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd 555787:7N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd!a$$Ifl6֞@Q""N-}24>, /%b444 layt :7;;;$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ;;;3<;<=<N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kda$$Ifl֞@Q""N-}24>, /%b444 layt =<===$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ==>>>>N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdb$$Ifl ֞@Q""N-}24>, /%b444 layt >?? ?$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  ? ???N@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdac$$Iflw֞@Q""N-}24>, /%b444 layt ?? ?!?"?$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd "?#?kd/d$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt #?(?????????$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  ???@@@N@@@@ $7$8$H$Ifgd kd`e$$Iflw֞@Q""N-}24>, /%b444 layt @@@@@$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd @@AAN@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd.f$$Iflw֞@Q""N-}24>, /%b444 layt AAAAA$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd AAkdf$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt A$AABBBB B$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  B BBBBBN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd-h$$Iflw֞@Q""N-}24>, /%b444 layt B,BBBBBBBeCgCkClCtCCCCCC*D+D-D0D1D9DYDDDDDD EvExE|E}EEEEEFF F%FFFGGQHRHZHpHHHJJJJJJJJJJJJJJJJnLpLγγ'hHB*CJOJPJQJ^JaJph hDA0h -h h B*CJOJPJQJ^JaJph3h h 5B*CJOJPJQJ\^JaJphFBBBBB,kd i$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd BB]CeCgChCjCkC$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd kClCtCCCCN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdi$$Iflw֞@Q""N-}24>, /%b444 layt CCCCC,kdj$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd C*D+D-D.D/D0D$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd 0D1Dkdk$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt 1D9DDDDDDD$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd DDDnEvExEN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdl$$Ifl֞@Q""N-}24>, /%b444 layt xEyE{E|E}E,kdm$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd }EEEEEEFF$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd FF FFFFN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdn$$Ifl֞@Q""N-}24>, /%b444 layt FNHPHQH$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd QHRHZHHHHN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdbo$$Ifl ֞@Q""N-}24>, /%b444 layt HJJJ$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd JJJJN@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd>p$$Ifl ֞@Q""N-}24>, /%b444 layt JJJJJ$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd JJkdq$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt JJJJJJJ$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd JJkdKr$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt JJfLnLpLqLsLtL$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd pLtLuL}LLLLLLLMMMMMMM#N%N)N*N2N7N=NNNNNNNNNN&O'O)O,O-O5OLONOOOOOOKPLPTPlPVQXQYQRR$R8RRRRRRRǜǜ'hpNB*CJOJPJQJ^JaJph-hn5B*CJOJPJQJ\^JaJph3h h 5B*CJOJPJQJ\^JaJph hDA0h -h h B*CJOJPJQJ^JaJph=tLuL}LLLLN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd|s$$Ifl?֞@Q""N-}24>, /%b444 layt LLLLL,kdXt$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd LLMMMMMM$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd MMMN#N%NN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd4u$$Ifl֞@Q""N-}24>, /%b444 layt %N&N(N)N*N,kdv$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd *N2NNNNNNN$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd NNNNN@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdv$$Ifl֞@Q""N-}24>, /%b444 layt NNNNN$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd NNkdw$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt N&O'O)O*O+O,O$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ,O-Okdx$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt -O5OOOOHPJPKP$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd KPLPTPEQNQVQN@@@@ $7$8$H$Ifgd kd*z$$Iflc֞@Q""N-}24>, /%b444 layt VQXQRRR$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd RR$RRRRN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdz$$Ifl֞@Q""N-}24>, /%b444 layt RRRRR,kd{$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd RRSSSRSTSUS$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd RSSUSVS^SwS3T5TTTTTUUUUUUUUUUUVVVVVVHWJWWWWWiXkXXXXX'Y)YGYHYQYdYYYYZZZZ [ [ [[[[[[γΟ'hzB*CJOJPJQJ^JaJph'hZB*CJOJPJQJ^JaJph hDA0h 3h h 5B*CJOJPJQJ\^JaJph-h h B*CJOJPJQJ^JaJph>USVS^S+T3T5TN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdx|$$Ifl֞@Q""N-}24>, /%b444 layt 5TTTT$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd TTTUUUN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd8}$$Ifl֞@Q""N-}24>, /%b444 layt UUUU$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd UUUUN@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd}$$Iflc֞@Q""N-}24>, /%b444 layt UUUUU$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd UUkd~$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt UUVVVVVV$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgdn $7$8$H$Ifgd VVV@WHWJWN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt JWWWW$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd WWW`XiXkXN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdŀ$$Ifl֞@Q""N-}24>, /%b444 layt kXXXX$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd XXXY'Y)YN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt )YDYFYGY$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd GYHYQYYYYN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdE$$Ifl֞@Q""N-}24>, /%b444 layt YZZZ$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ZZZ[ [ [N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt  [}[[[$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd [[[[[[N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdŃ$$Ifl`֞@Q""N-}24>, /%b444 layt [[[h\i\r\\+]-]]]]]-^/^z^{^^^_!_h_j___<`=`?`B`C`L`Z```aaaaaaUbWbbbCcDcMccccccd dddѺ庳庳废庳庳庋庋庳'hx/^B*CJOJPJQJ^JaJph'hGB*CJOJPJQJ^JaJph hDA0h -h h B*CJOJPJQJ^JaJph'hZB*CJOJPJQJ^JaJph3h h 5B*CJOJPJQJ\^JaJph6[e\g\h\$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd h\i\r\]"]+]N@@@@ $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt +]-]]]]$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd ]]]$^-^/^N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdE$$IflW֞@Q""N-}24>, /%b444 layt /^w^y^z^$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd z^{^^__h_j_N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt j____$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd __<`=`N@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdņ$$Ifl֞@Q""N-}24>, /%b444 layt =`?`@`A`B`$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd B`C`kd$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt C`L````aaa$$7$8$H$Ifa$gd  $7$8$H$Ifgdx/^$$7$8$H$Ifa$gd  $7$8$H$Ifgd aaa$b.b8bBbLbN@@@@@@ $7$8$H$Ifgd kdĈ$$Ifl֞@Q""N-}24>, /%b444 layt LbUbWb@cBcCc$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd CcDcMccccN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt cccc$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd cd ddddN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdR$$Ifl֞@Q""N-}24>, /%b444 layt ddddddddddeeeeef ffffffff'g)g-g.g7gDggg hhh'hthvhzh{hhhhh;i, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd dddddddd$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ddeeeeN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdҋ$$Ifl֞@Q""N-}24>, /%b444 layt eeeef,kd$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd f fffffff$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd fffg'g)gN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdR$$Ifl֞@Q""N-}24>, /%b444 layt )g*g,g-g.g,kd$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd .g7gggg h h h$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  hhhkhthvhN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdҎ$$Ifl0֞@Q""N-}24>, /%b444 layt vhwhyhzh{h,kd$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd {hhhhh8i:i;i$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ;i, /%b444 layt ijjj$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd jjjjjjN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt jjjjj,kdґ$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd jjk(k*kkkk$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd kkklllN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt llll$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd lllll*m,mmmmmmmmmm"n$nnnnnooooopNpPppppp`qbqtqqqqrrr!r#rBrerrrrrrrrrrrssRsTsssssItKtxtyttt'hoB*CJOJPJQJ^JaJph3h h 5B*CJOJPJQJ\^JaJph hDA0h -h h B*CJOJPJQJ^JaJphFlll!m*m,mN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdR$$Ifl'֞@Q""N-}24>, /%b444 layt ,mmmm$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd mmmmN@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt mmmmm$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd mmkd$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt mmn"n$nnnn$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd nnnoooooN@@@@@@ $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt ooooo$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd oooFpNpPpN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdߖ$$Ifl֞@Q""N-}24>, /%b444 layt Ppppp$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd pppXq`qbqN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt bqrrr$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$IfgdorrrrrrN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd_$$Iflo֞@Q""N-}24>, /%b444 layt rrrr$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd rrrrN@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt rrrrr$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd rrkd$$Ifl3ֈ@""N-}24>, /% <b444 lap<yt rsJsRsTssss$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd sssAtItKtN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$IflW֞@Q""N-}24>, /%b444 layt Ktutwtxt$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd xtytttuuN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt tuuvuwuuuvv*vJvUvVv^vivvvvvvw^w`wwwwwwwwwwxxxxxxyyyyyy6z8zIzJzQzlzzzzzzz9{={I{J{P{T{{{4|5|;|O||||'hoB*CJOJPJQJ^JaJph hDA0h 3h h 5B*CJOJPJQJ\^JaJph-h h B*CJOJPJQJ^JaJphFusuuuvu$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd vuwuuvvvN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt vRvTvUv$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd UvVv^vvvvN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdl$$Ifl֞@Q""N-}24>, /%b444 layt vvvv$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd vvvUwVw^wN@@@@ $7$8$H$Ifgd kd,$$Ifl֞@Q""N-}24>, /%b444 layt ^w`wwww$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd wwwwN@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt wwwww$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd wwkd$$Iflֈ@""N-}24>, /% <b444 lap<yt wwxxxxxx$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd xxxyyyN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Iflw֞@Q""N-}24>, /%b444 layt yyyy$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd yyy0z6z8zN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdǡ$$IflH֞@Q""N-}24>, /%b444 layt 8zFzHzIz$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd IzJzQzzzzN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt zzzzz,kd$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd zz3{9{={>{H{I{$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd I{J{P{{{{N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd[$$Ifl֞@Q""N-}24>, /%b444 layt {)|3|4|$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd 4|5|;||||N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd7$$IflH֞@Q""N-}24>, /%b444 layt |||||,kd$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd |||||}}}}h}j}l}~~~~~~  ACGHNU !()*018;E‚ۂ01ߴ'hoB*CJOJPJQJ^JaJph-h h B*CJOJPJQJ^JaJph3h h 5B*CJOJPJQJ\^JaJph hDA0h G||||||}$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd }}kd$$Iflֈ@""N-}24>, /% <b444 lap<yt }}b}h}j}~~~$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd ~~~~~~N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd $$Ifl=֞@Q""N-}24>, /%b444 layt ~~,kd$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd N@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdة$$Ifl֞@Q""N-}24>, /%b444 layt ,kd$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd ;ACDFG$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd GHNN@@@/$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdf$$Ifl֞@Q""N-}24>, /%b444 layt ,kd&$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  !"#$%&N=====$$7$8$H$Ifa$gd kd$$Ifl֞@Q""N-}24>, /%b444 layt &'()*,kd$$Ifl֞@Q""N-}24>, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd *+,-./0$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd 018N@@//$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt ?1 $7$8$H$Ifgd kd&$$Iflֈ@Q""N-}24, /%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd eW $7$8$H$Ifgd wkd$$Ifl\@QN-}24(/%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd ‚Â./0}$$7$8$H$Ifa$gd  $7$8$H$Ifgd $$7$8$H$Ifa$gd Qkd6$$Ifl0@Q4Q0b444 layt 012345678vvvvvev$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd wkd$$Ifl\@QN-}24(/%b444 layt 189UZ[؃ك;<%&()3OӉՉ։&'IJLOPX᯦mffmmfm hDA0hp-hphpB*CJOJPJQJ^JaJph3hphp5B*CJOJPJQJ\^JaJphhChs~h 5KH$\h 'hoB*CJOJPJQJ^JaJph3h h 5B*CJOJPJQJ\^JaJph hDA0h -h h B*CJOJPJQJ^JaJph(89UVWXN@///$$7$8$H$Ifa$gd  $7$8$H$Ifgd kd$$Ifl֞@Q""N-}24>, /%b444 layt XYZ$$7$8$H$Ifa$gd $$7$8$H$Ifa$gd Z[kd$$Iflֈ@""N-}24>, /% <b444 lap<yt [`փ׃؃كރ789:Wwkd$$Ifl\@QN-}24(/%b444 layt $$7$8$H$Ifa$gd $$7$8$H$Ifa$gd  $7$8$H$Ifgd  :;<APBB1$$7$8$H$Ifa$gd  $7$8$H$Ifgd kdy$$Iflֈ@Q""N-}24, /%b444 layt $$7$8$H$Ifa$gd vhhW$$7$8$H$Ifa$gd  $7$8$H$Ifgd wkd$$Ifl\@QN-}24(/%b444 layt $$7$8$H$Ifa$gd AB݅ޅaSSSSSSS $7$8$H$Ifgd kd$$Iflֈ@Q""N-}24, /%b444 layt %?Qkd}$$Iflw0@Q4Q0b444 layt  $7$8$H$Ifgdo $7$8$H$Ifgd Qkd$$Ifl0@Q4Q0b444 layt %&')OyӉԉՉ$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpgd:wQkd۵$$Ifl0@Q4Q0b444 layt  Չ։މ  aPPPPPPPP$$7$8$H$Ifa$gdpkd9$$Ifl*ֈ#-18N 244 laNytp &'I=/ $7$8$H$IfgdpkdM$$Iflw֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdpIJLMNO$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpOPkd7$$Ifl3ֈ#-18N 2 <44 laNp<ytpPXR-5=?ٍڍۍ܍ލߍ$$7$8$H$Ifa$gdp $7$8$H$IfgdpXb=? Џ0&(TU]mTV )-?@IZ MNW_ %iknopz؞ڞޞߞkmst hDA0hp-hphpB*CJOJPJQJ^JaJph3hphp5B*CJOJPJQJ\^JaJphN iN@@@@@@ $7$8$H$Ifgdpkdh$$Iflj ֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpy~N@@@@@@ $7$8$H$IfgdpkdD$$Ifl.֞/#-18MN 244 laNytpԑՑߑ$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp &(N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd $$IflZ֞/#-18MN 244 laNytp(/QST$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpTU]LTVN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$IflH֞/#-18MN 244 laNytpV$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@2@@ $7$8$H$Ifgd $7$8$H$Ifgdpkdؼ$$IflH֞/#-18MN 244 laNytp $7$8$H$Ifgdp$$7$8$H$Ifa$gdp  #)N@@@@@@ $7$8$H$Ifgdpkd$$IflW֞/#-18MN 244 laNytp)-.?@I?1 $7$8$H$Ifgdpkd$$Iflnֈ/#-8MN D 44 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpIјܘ$$7$8$H$Ifa$gdp $7$8$H$Ifgdp N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd^$$Ifl֞/#-18MN 244 laNytpJLM$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpMNWN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd:$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp S_iN@@@@ $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpiklno$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpopzΞ؞ڞN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpڞ۞ݞޞߞ,kd$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpߞbkmnrs$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpstN@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpt(*./7J,.}$9-/34<Q;=¦DFLMVcʧ̧Чѧ٧(*./jkmpqyγγ'hB*CJOJPJQJ^JaJph hDA0hp-hphpB*CJOJPJQJ^JaJph3hphp5B*CJOJPJQJ\^JaJphF$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpkd$$Ifl?ֈ#-18N 2 <44 laNp<ytp (*+-.$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp./7$,.N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytp. $7$8$H$Ifgdp$$7$8$H$Ifa$gdp $7$8$H$Ifgd$ݣN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl*֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp%-/N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkdo$$Ifl֞/#-18MN 244 laNytp/0234,kdK$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp4<3;=$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgd $7$8$H$Ifgdp<DFN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd'$$Ifl֞/#-18MN 244 laNytpFGKLM,kd$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpMVʧ̧ͧϧЧ$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpЧѧ٧N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytp,kd$$Iflw֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp (*+-.$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp./jkN@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpkmnop$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdppqkds$$Ifl3ֈ#-18N 2 <44 laNp<ytpqy$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp.045=Zí  ,3589[bdghͮԮ֮ٮڮ  LSUXYįů-469: hDA0hp3hphp5B*CJOJPJQJ\^JaJph-hphpB*CJOJPJQJ^JaJphNN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$IflH֞/#-18MN 244 laNytp,kdr$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpǫ¬&.0134$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp 45=N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd2$$Ifl(֞/#-18MN 244 laNytp,kd$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp   $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp,35N@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytp5678$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp89kd$$Ifl3ֈ#-18N 2 <44 laNp<ytp9[bdefg$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpghkd$$Ifl3ֈ#-18N 2 <44 laNp<ytph$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl3ֈ#-18N 2 <44 laNp<ytpͮԮ֮׮خٮ$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpٮڮkd$$Ifl3ֈ#-18N 2 <44 laNp<ytpڮ    $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp kd$$Ifl3ֈ#-18N 2 <44 laNp<ytpLSUVWX$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpXYkd=$$Ifl3ֈ#-18N 2 <44 laNp<ytpY$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd`$$Ifl3ֈ#-18N 2 <44 laNp<ytp¯ïį$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpįůkd$$Ifl3ֈ#-18N 2 <44 laNp<ytpů$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl3ֈ#-18N 2 <44 laNp<ytp-46789$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp9:kd$$Ifl3ֈ#-18N 2 <44 laNp<ytp:krtuvw$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp:krtwx°?A±ñȱòӲ/1  uzϵѵ =¶HJnot%'./4E +γγ'h_B*CJOJPJQJ^JaJph hDA0hp-hphpB*CJOJPJQJ^JaJph3hphp5B*CJOJPJQJ\^JaJphFwxkd$$Ifl3ֈ#-18N 2 <44 laNp<ytpx$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl3ֈ#-18N 2 <44 laNp<ytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd@$$Ifl3ֈ#-18N 2 <44 laNp<ytp%/9?A±$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp ±ñȱN@@@@@@ $7$8$H$Ifgdpkdq$$IflH֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdpò'/1N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd?$$IflH֞/#-18MN 244 laNytp1$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Iflw֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgd_ }N@@@@@ $7$8$H$Ifgdpkd$$Ifl" ֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdp6@HN@@@@ $7$8$H$Ifgdpkd$$Iflw֞/#-18MN 244 laNytpHJkmn$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdpnot%'N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd?$$Ifl֞/#-18MN 244 laNytp'+-.$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp./4̸ո޸N@@@@@@ $7$8$H$Ifgdpkd$$IflT֞/#-18MN 244 laNytpȹʹ˹$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdp+[`˹̹ѹNSŻ׻~IK@ACFGLf7>^̿ѿ5W\89>Hγ'h_B*CJOJPJQJ^JaJph hDA0hp3hphp5B*CJOJPJQJ\^JaJph-hphpB*CJOJPJQJ^JaJphF˹̹ѹxN@@@@@@ $7$8$H$Ifgdpkd$$Ifl6֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp $7$8$H$Ifgd_$$7$8$H$Ifa$gdpŻZclv~N@@@@@@ $7$8$H$Ifgdpkd$$Iflc֞/#-18MN 244 laNytp~$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdp@AN@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd?$$Ifl ֞/#-18MN 244 laNytpACDEF$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpFGkd $$Ifl3ֈ#-18N 2 <44 laNp<ytpGL&/79$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp N@@@@@@ $7$8$H$Ifgdpkd>$$Ifl: ֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdpt~N@@@@@@ $7$8$H$Ifgdpkd $$IflH֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdpOWYN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$IflH֞/#-18MN 244 laNytpY578$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp89>N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl"֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpflnN@@@/$$7$8$H$Ifa$gdp $7$8$H$IfgdpkdL$$Ifl֞/#-18MN 244 laNytpln79abgrQSrsx!./5Dgl ')VW]s,.67=l +3hphp5B*CJOJPJQJ\^JaJph hDA0hp3hphp5B*CJOJPJQJ\^JaJph-hphpB*CJOJPJQJ^JaJph@n$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp/79N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd $$Ifl֞/#-18MN 244 laNytp9^`a$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpabgIQSN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpSoqr$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdprsx!N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Iflw֞/#-18MN 244 laNytp!+-.$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp./5N@@@/$$7$8$H$Ifa$gdp $7$8$H$IfgdpkdL$$Iflw֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@@@@@@ $7$8$H$Ifgdpkd $$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp')N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytp)SUV$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpVW]$,N@@@@@ $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytp,.356$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdp67=N@@@/$$7$8$H$Ifa$gdp $7$8$H$IfgdpkdL$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd $$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpKN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytp,1GM6<klr  -ѷѷќтѷѷќтѷѷќѷѷѷќѷќѷѷќѷѷѷѷ3hphp5B*CJOJPJQJ\^JaJph hDA0hp'h_B*CJOJPJQJ^JaJph3hphp5B*CJOJPJQJ\^JaJph-hphpB*CJOJPJQJ^JaJph-hphpB*CJOJPJQJ^JaJph3$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$GIN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpI$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp.68N@@@/$$7$8$H$Ifa$gdp $7$8$H$IfgdpkdL$$Iflc֞/#-18MN 244 laNytp8hjk$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpklr  N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd $$Iflc֞/#-18MN 244 laNytp $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpkd$$Ifl3ֈ#-18N 2 <44 laNp<ytp $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp N@@@@ $7$8$H$Ifgdpkd$$Iflw֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdp "%&.J 6oquv~457:;CcNPTU]n!;<opqtu3hphp5B*CJOJPJQJ\^JaJph hDA0hp-hphpB*CJOJPJQJ^JaJphN N@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$IflH֞/#-18MN 244 laNytp "#$%$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp%&kdg$$Ifl3ֈ#-18N 2 <44 laNp<ytp&. $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytp,kdt$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpgoqrtu$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpuv~N@@@/$$7$8$H$Ifa$gdp $7$8$H$IfgdpkdP$$Iflw֞/#-18MN 244 laNytp,kd,$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp45789:$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp:;kd$$Ifl3ֈ#-18N 2 <44 laNp<ytp;C$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpFNPN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd9$$Ifl֞/#-18MN 244 laNytpPQSTU,kd$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpU]$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp~N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Iflw֞/#-18MN 244 laNytp,kd$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp!8:;$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp;<opN@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytppqrst$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdptukd$$Ifl3ֈ#-18N 2 <44 laNp<ytpu$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl3ֈ#-18N 2 <44 laNp<ytp$&$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$&46:;CUqswx  3469:tuwz{&:'h|B*CJOJPJQJ^JaJph-h5B*CJOJPJQJ\^JaJph hDA0hp3hphp5B*CJOJPJQJ\^JaJph-hphpB*CJOJPJQJ^JaJph=,46N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytp679:;,kd$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp;C$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpiqsN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd $$Ifl֞/#-18MN 244 laNytpstvwx,kd{ $$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpx $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp  34N@/$$7$8$H$Ifa$gdp $7$8$H$IfgdpkdW $$Ifl֞/#-18MN 244 laNytp46789$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp9:kd3 $$Ifl3ֈ#-18N 2 <44 laNp<ytp:tuwxyz$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpz{kdd $$Ifl3ֈ#-18N 2 <44 laNp<ytp{$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@@@@ $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdp&N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkdc$$IflH֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp;CEN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd#$$Ifl֞/#-18MN 244 laNytpCEvwTVXZt   01256>Tΰq-h`5B*CJOJPJQJ\^JaJph'hB*CJOJPJQJ^JaJph'hmB*CJOJPJQJ^JaJph-h5B*CJOJPJQJ\^JaJph hDA0hp3hphp5B*CJOJPJQJ\^JaJph-hphpB*CJOJPJQJ^JaJph,Esuv$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpvwLTVN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpV$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpPXZN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpZ$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp4& $7$8$H$Ifgdpkdc$$Iflw֞/#-18MN 2 44 laNpytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpkdf$$Ifl3ֈ#-18N 2 <44 laNp<ytp 245$$7$8$H$Ifa$gdp $7$8$H$Ifgd`$$7$8$H$Ifa$gdp $7$8$H$Ifgdp56>N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl`֞/#-18MN 244 laNytpT    rteg_aSUst}ac'h?HB*CJOJPJQJ^JaJph hDA0hp-h`5B*CJOJPJQJ\^JaJph3hphp5B*CJOJPJQJ\^JaJph-hphpB*CJOJPJQJ^JaJph=$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgd` N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkde$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd%$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpirtN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpt$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp\egN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpg$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkde$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpLV_N@@@@ $7$8$H$Ifgdpkd%$$Ifl֞/#-18MN 244 laNytp_a$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdpJSUN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpUprs$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpst}XacN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpc$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkde$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpkd3$$Ifl3ֈ#-18N 2 <44 laNp<ytp_axzLNsy)*EFO^@Bkmqr{34=Mȝ'h?HB*CJOJPJQJ^JaJph-hph?HB*CJOJPJQJ^JaJph3hphp5B*CJOJPJQJ\^JaJph-hphpB*CJOJPJQJ^JaJph hDA0hp>V_a$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpU_is}N@@@@@@ $7$8$H$Ifgdpkdd$$IflH֞/#-18MN 244 laNytp}$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpoxzN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd2$$Ifl֞/#-18MN 244 laNytpz$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpCLNN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl֞/#-18MN 244 laNytpN$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$Ifl6֞/#-18MN 244 laNytpBDE$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpEFO7@BN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkdr $$Ifl֞/#-18MN 244 laNytpB$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpzN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd2!$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpbkmN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd!$$Ifl֞/#-18MN 244 laNytpmnpqr,kd"$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpr{023$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp34=N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkdr#$$Ifl֞/#-18MN 244 laNytpM "#$%#%df>PQZd./8G;<>ABJ\.0κκΟ'h=B*CJOJPJQJ^JaJph hDA0hp'h?HB*CJOJPJQJ^JaJph3hphp5B*CJOJPJQJ\^JaJph-hphpB*CJOJPJQJ^JaJph>$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp "N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd2$$$Ifl֞/#-18MN 244 laNytp"$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp#%N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd$$$Ifl֞/#-18MN 244 laNytp%$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp[dfN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd%$$Ifl*֞/#-18MN 244 laNytpf}$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkdr&$$Ifl֞/#-18MN 244 laNytpMOP$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpPQZN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd2'$$Ifl֞/#-18MN 244 laNytp+-.$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp./8N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd'$$Ifl"֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp;<N@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd($$Ifl֞/#-18MN 244 laNytp<>?@A$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpABkd)$$Ifl3ֈ#-18N 2 <44 laNp<ytpBJ$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp&.N@@@@@@ $7$8$H$Ifgdpkd*$$Ifl֞/#-18MN 244 laNytp.0$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdp0 !ST\q.0 !"\^_kl| }     \ ] e s   9 : B U       ? A t u }       dzdz'h=B*CJOJPJQJ^JaJph3hphp5B*CJOJPJQJ\^JaJph hDA0hp-hphpB*CJOJPJQJ^JaJphF N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd+$$Ifl֞/#-18MN 244 laNytp PRS$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpST\&.0N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd?,$$Ifl֞/#-18MN 244 laNytp0$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpT\^N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd,$$Ifl֞/#-18MN 244 laNytp^hjk$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpklN@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd-$$Ifl ֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpkd.$$Ifl3ֈ#-18N 2 <44 laNp<ytpy { | $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp| }     N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd/$$Ifl?֞/#-18MN 244 laNytp Y [ \ $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp\ ] e    N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd0$$Ifl֞/#-18MN 244 laNytp 6 8 9 $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp9 : B    N@@@/$$7$8$H$Ifa$gdp $7$8$H$IfgdpkdL1$$IflQ֞/#-18MN 244 laNytp     ,kd 2$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp  7 ? A q s t $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdpt u }    N@@@@ $7$8$H$Ifgdpkd2$$Ifl֞/#-18MN 244 laNytp     $$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdp    N@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd3$$Ifl֞/#-18MN 244 laNytp       ~2489@[*.;<BF57=>stvyz xz~  rtxy hDA0hp3hphp5B*CJOJPJQJ\^JaJph-hphpB*CJOJPJQJ^JaJphN     $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp  kdZ4$$Iflֈ#-18N 2 <44 laNp<ytp  x~$$7$8$H$Ifa$gdp $7$8$H$IfgdpN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd5$$Iflw֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp,24N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkdg6$$IflH֞/#-18MN 244 laNytp45789,kdC7$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp9@$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$*.N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd8$$Ifl֞/#-18MN 244 laNytp./;<B?11 $7$8$H$Ifgdpkd8$$Iflֈ/#-8MN D 44 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp1kd9$$Iflֈ/#-8MN D 44 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp/578<=$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp=>stN@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd:$$Ifl֞/#-18MN 244 laNytptvwxy$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpyzkds;$$Iflֈ#-18N 2 <44 laNp<ytpz$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdprxzN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd<$$Ifl֞/#-18MN 244 laNytpz{}~,kd=$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp  $$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdplrtN@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd\>$$Ifl֞/#-18MN 244 laNytptuwxy,kd*?$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpy$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$Ifgdp!#'(.4  ~?@Yhúv-h50h50B*CJOJPJQJ^JaJph hDA0h503h50h505B*CJOJPJQJ\^JaJphho{h50hs~hp5KH$\hp hDA0hp-hphpB*CJOJPJQJ^JaJph3hphp5B*CJOJPJQJ\^JaJph.!#N@@@/$$7$8$H$Ifa$gdp $7$8$H$Ifgdpkd?$$Ifl֞/#-18MN 244 laNytp#$&'(,kd@$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp(.$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp $7$8$H$IfgdpN=====$$7$8$H$Ifa$gdpkdjA$$Ifl֞/#-18MN 244 laNytp,kd*B$$Ifl֞/#-18MN 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdpN@@//$$7$8$H$Ifa$gdp $7$8$H$IfgdpkdC$$Ifl֞/#-18MN 244 laNytp   |?1 $7$8$H$IfgdpkdC$$Iflֈ/#-18M}N 244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp|}~?eW $7$8$H$Ifgdpwkd@D$$Ifl\/-18M*244 laNytp$$7$8$H$Ifa$gdp$$7$8$H$Ifa$gdp?@A}$$7$8$H$Ifa$gdp $7$8$H$Ifgdp$$7$8$H$Ifa$gdpQkdD$$Ifl0/8M444 laNytp49?Jpoooooooo$$7$8$H$Ifa$gd50gd:wwkdE$$Ifl\/-18M*244 laNytp vveeeveeee$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50wkdE$$Ifl\JP844 laNyt )*/12:D!hiq~   """"##Y$Z$b$r$Y%[%%%%%&&T'U'_'m'~((() ))**++++--8-9-m-n-w---'hqy:B*CJOJPJQJ^JaJph hDA0h503h50h505B*CJOJPJQJ\^JaJph-h50h50B*CJOJPJQJ^JaJphF;***$$7$8$H$Ifa$gd50kdRF$$IflִJ~'o,}/P84    44 laNyt$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50)*;-$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50kdG$$Ifl-ִJ#~'}/P8    44 laNyt*,-./012:x4!#%&(h $7$8$H$Ifgd50Ff+J$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50hiq( $7$8$H$Ifgd50kdjL$$IflX J#~'o,}/P8$$$$44 laNytqw 1$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 h;---- $7$8$H$Ifgd50kdbM$$IflִJ#o,}/P8    44 laNytm       !A!E!"$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 """##;--- $7$8$H$Ifgd50kdLN$$IflXִJ#o,}/P8    44 laNyt###V$X$Y$ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50Y$Z$b$Q%Y%;--- $7$8$H$Ifgd50kd6O$$IflִJ#o,}/P8    44 laNytY%[%%%%% $7$8$H$Ifgd50$$7$8$H$Ifa$gd50%%%&&&;---- $7$8$H$Ifgd50kd P$$IflִJ#o,}/P8    44 laNyt&&3'Q'S'T' $7$8$H$Ifgd50$$7$8$H$Ifa$gd50T'U'_'`(j(q(;---- $7$8$H$Ifgd50kd Q$$IflִJ#o,}/P8    44 laNytq(x(~((((((($$7$8$H$Ifa$gd50 $7$8$H$Ifgd50() )( $7$8$H$Ifgd50kdQ$$Ifl J#~'o,}/P8$$$$44 laNyt )*****9+;++$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50+++,-;--- $7$8$H$Ifgd50kdR$$IflִJ#o,}/P8    44 laNyt--- - - -m- $7$8$H$Ifgd50$$7$8$H$Ifa$gd50m-n-w-( $7$8$H$Ifgd50kdS$$Ifl J#~'o,}/P8$$$$44 laNytw----.///$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50--..//&/8/|0~00011%12122333344444444444n5p55555667777999:: :::::::;;;;;;^<`<<<<<==κγκγγγγγγγγγγ hDA0h50'hqy:B*CJOJPJQJ^JaJph-h50h50B*CJOJPJQJ^JaJph3h50h505B*CJOJPJQJ\^JaJphF//&/f0r0|0;---- $7$8$H$Ifgd50kdT$$IflִJ#o,}/P8    44 laNyt|0~00111 $7$8$H$Ifgd50$$7$8$H$Ifa$gd5011%1y22;--- $7$8$H$Ifgd50kdU$$IflִJ#o,}/P8    44 laNyt22K3333 $7$8$H$Ifgd50$$7$8$H$Ifa$gd50333 44;--- $7$8$H$Ifgd50kdV$$Ifl ִJ#o,}/P8    44 laNyt44r4444 $7$8$H$Ifgd50$$7$8$H$Ifa$gd504444;-$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50kdW$$IflִJ#o,}/P8    44 laNyt444444444f5n5p5r5t5u5w55FfY $7$8$H$Ifgd50$$7$8$H$Ifa$gd50555( $7$8$H$Ifgd50kd.\$$Iflb J#~'o,}/P8$$$$44 laNyt56666667$$7$8$H$Ifa$gd50 $7$8$H$Ifgd5077799;--- $7$8$H$Ifgd50kd&]$$IflִJ#o,}/P8    44 laNyt999999 $7$8$H$Ifgd50$$7$8$H$Ifa$gd509::::;--- $7$8$H$Ifgd50kd^$$IflִJ#o,}/P8    44 laNyt::::::: $7$8$H$Ifgd50$$7$8$H$Ifa$gd50:::( $7$8$H$Ifgd50kd^$$IflF J#~'o,}/P8$$$$44 laNyt:;;;;;;;;$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50;;;( $7$8$H$Ifgd50kd_$$Iflw J#~'o,}/P8$$$$44 laNyt;V<^<`<b<<<<$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50<<<<=;--- $7$8$H$Ifgd50kd`$$IflFִJ#o,}/P8    44 laNyt== = = ==.= $7$8$H$Ifgd50$$7$8$H$Ifa$gd50=.=/=7=T===>> >>>>>>>>>>>>>??@@@@AA9A:ABARAbCdCCCCCCCDD DD^D`DhDiDDDDDDDDDDDDDDDD,E3E5E:E;EbEiEkEpEqEEEEE3h50h505B*CJOJPJQJ\^JaJph hDA0h50-h50h50B*CJOJPJQJ^JaJphN.=/=7=( $7$8$H$Ifgd50kda$$IflF J#~'o,}/P8$$$$44 laNyt7======>>>$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50>> >( $7$8$H$Ifgd50kdb$$Ifl J#~'o,}/P8$$$$44 laNyt >>>>>>>>>$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50>>>( $7$8$H$Ifgd50kdc$$IflF J#~'o,}/P8$$$$44 laNyt>>>>>>>>>>???@@@@@Ff5f $7$8$H$Ifgd50$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50@@@( $7$8$H$Ifgd50kdth$$Ifl J#~'o,}/P8$$$$44 laNyt@ AAAAAAA9A$$7$8$H$Ifa$gd50 $7$8$H$Ifgd509A:ABA( $7$8$H$Ifgd50kd^i$$IflL J#~'o,}/P8$$$$44 laNytBAAB:CZCbCdCfChCiCkCC$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 CCC( $7$8$H$Ifgd50kd:j$$Iflj J#~'o,}/P8$$$$44 laNytCCCCCDDDD$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50DD D( $7$8$H$Ifgd50kdk$$IflF J#~'o,}/P8$$$$44 laNyt DVD^D`DbDdDeDgDhD$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50hDiDD( $7$8$H$Ifgd50kdk$$Ifl J#~'o,}/P8$$$$44 laNytDDDDDDDDDDDDDDDDDDDDDDDDDFfqFfUn$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50DDD,E3E5E6E7E8E9E:E;EbEiEkElEmEnEoEpEqEEEEEFf|FfSy$$7$8$H$Ifa$gd50Ffu $7$8$H$Ifgd50EEEEEEEEEEEEEEEF&F(F)F*F+F,F-F.FaFFfFfQ$$7$8$H$Ifa$gd50Ff $7$8$H$Ifgd50EEEEEEEF&F(F-F.FaFhFjFoFpFFFFFFFFFFFFGGG GGGG#G$G)G5GGGIHJHOHnH-I/I6ILȴȴ'hqy:B*CJOJPJQJ^JaJph-h50h50B*CJOJPJQJ^JaJph3h50h505B*CJOJPJQJ\^JaJph hDA0h50GaFhFjFkFlFmFnFoFpFFFFFFFFFFFFFFFFFFfOFf$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50FFFFGGGGGGG GGGGG G!G"G#G$G)GGFfi$$7$8$H$Ifa$gd50Ff$$7$8$H$Ifa$gd50Ff $7$8$H$Ifgd50GGGGGGGGGGIH$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 IHJHOH( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNytOH III'I-I/I1I3I4I6IHI$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 HIIINI( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNytNIIIIIIIIJ$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50JJJ( $7$8$H$Ifgd50kdn$$Ifl J#~'o,}/P8$$$$44 laNytJ(K0K2K4K6K7K9KK$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50KKK( $7$8$H$Ifgd50kdJ$$Ifl< J#~'o,}/P8$$$$44 laNytKLL&L.L0L2L4L5L7L8L$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 8L9L>L( $7$8$H$Ifgd50kd&$$Ifl J#~'o,}/P8$$$$44 laNyt>LSLLL(M)M.MGMMMMMMNNNOOO4OOO`PaPgPyP Q"QQQQQQQQRRR"RRRSSSSTTMUNUSUUUUVVV*VVV@W`W'Y(YγΟ'h+aB*CJOJPJQJ^JaJph'hqy:B*CJOJPJQJ^JaJph hDA0h50-h50h50B*CJOJPJQJ^JaJph3h50h505B*CJOJPJQJ\^JaJph>>LLLLLLLLL(M$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 (M)M.M( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNyt.MMMMMMMMM$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50MMM( $7$8$H$Ifgd50kdޡ$$Ifl J#~'o,}/P8$$$$44 laNytMNNNNNNNNNNO$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 OOO( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNytOOOOOOOOOOO`P$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 `PaPgP( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNytgPPQQQ Q"Q$Q&Q'Q)QQ$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 QQQ( $7$8$H$Ifgd50kdr$$Ifl2 J#~'o,}/P8$$$$44 laNytQQQQQRRRRRRRRRRRRRRSFfզ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50SSS( $7$8$H$Ifgd50kd$$Ifl  J#~'o,}/P8$$$$44 laNytSTTTTTTTTTTMU $7$8$H$Ifgd+a$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 MUNUSU( $7$8$H$Ifgd50kd$$Ifl^ J#~'o,}/P8$$$$44 laNytSUUUUUUUUUUUV$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 VVV( $7$8$H$Ifgd50kdڪ$$Ifl J#~'o,}/P8$$$$44 laNytVVVVVVVV'Y$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50'Y(Y-Y( $7$8$H$Ifgd50kd$$Ifl$  J#~'o,}/P8$$$$44 laNyt(Y-Y7YYYYYYYAZCZZZZZX[Z[b[c[h[s[R\T\\\]]]]G^I^Q^R^X^g^_ _(_)_/_F___``````/a1aaabbbbbbbccc.d/d5dQdddrese'h+aB*CJOJPJQJ^JaJph hDA0h503h50h505B*CJOJPJQJ\^JaJph-h50h50B*CJOJPJQJ^JaJphF-YYYYYYYYY$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50YYY( $7$8$H$Ifgd50kd$$IflF J#~'o,}/P8$$$$44 laNytY;ZAZCZEZIZJZNZZ$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50ZZZ( $7$8$H$Ifgd50kdn$$Ifl J#~'o,}/P8$$$$44 laNytZP[X[Z[\[^[_[a[b[$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50b[c[h[( $7$8$H$Ifgd50kdJ$$IflF J#~'o,}/P8$$$$44 laNyth[J\R\T\V\X\Y\[\]$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50]]]( $7$8$H$Ifgd50kd&$$Ifl J#~'o,}/P8$$$$44 laNyt]?^G^I^K^M^N^P^Q^$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50Q^R^X^( $7$8$H$Ifgd50kd$$IflF J#~'o,}/P8$$$$44 laNytX^__ _"_$_%_'_(_$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50(_)_/_( $7$8$H$Ifgd50kdް$$Ifl J#~'o,}/P8$$$$44 laNyt/_____________`$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 ```( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNyt`'a/a1a3a5a6a8aa$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50aab( $7$8$H$Ifgd50kd$$IflS J#~'o,}/P8$$$$44 laNytbbbbbbbbbbb$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 bbb( $7$8$H$Ifgd50kdr$$Ifl J#~'o,}/P8$$$$44 laNytbccccccc.d$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50.d/d5d( $7$8$H$Ifgd50kdN$$Ifl2 J#~'o,}/P8$$$$44 laNyt5ddddddddre$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50reseye( $7$8$H$Ifgd50kd*$$Ifl2 J#~'o,}/P8$$$$44 laNytseyeeevfxfffff-h/hhhiiii\j^jejfjljjkk,l-l?l@lBlGlHlMlmllm(n)n.nQnooqqqqqqqr#rη薝薝'h+aB*CJOJPJQJ^JaJph hDA0h503h50h505B*CJOJPJQJ\^JaJph-h50h50B*CJOJPJQJ^JaJph3h50h505B*CJOJPJQJ\^JaJph-h50h50B*CJOJPJQJ^JaJph3yefvfxf|fffff$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50fff( $7$8$H$Ifgd50kd$$Iflb J#~'o,}/P8$$$$44 laNytf h-h/h1h3h4h6hi $7$8$H$Ifgd+a$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50iii( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNytiTj\j^j`jbjcjdjej$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50ejfjlj( $7$8$H$Ifgd50kd$$IflF J#~'o,}/P8$$$$44 laNytljjkkk k k k,l$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50,l-l?l( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNyt?l@lBlClDlElFlGlHlMlllllmmmmm(nFf $7$8$H$Ifgd50$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50(n)n.n( $7$8$H$Ifgd50kd<$$Ifl J#~'o,}/P8$$$$44 laNyt.n ooooo o!o#oq$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 qqq( $7$8$H$Ifgd50kd&$$Ifl  J#~'o,}/P8$$$$44 laNytqqqqqqqqqrrrrrrrrrFf $7$8$H$Ifgd50$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50#rrrrrrsssssssPtRtZt[tctntttttuu u%u&u.uNuuuuuuu=v?v-w.w6wGwwww8x9xAx\xxxxxxxhyjyrysyyyyyyyyyyyyyγ'ht =B*CJOJPJQJ^JaJph hDA0h503h50h505B*CJOJPJQJ\^JaJph-h50h50B*CJOJPJQJ^JaJphFrrr( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNytrssssssss$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50sss( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNytsHtPtRtTtVtWtYtZt$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50Zt[tct( $7$8$H$Ifgd50kd$$IflF J#~'o,}/P8$$$$44 laNytcttttttttt$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50ttu( $7$8$H$Ifgd50kd$$IflF J#~'o,}/P8$$$$44 laNytuu u!u"u#u$u%u&u.uuuuuuuuuFf! $7$8$H$Ifgd50$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50uuu( $7$8$H$Ifgd50kd`$$IflF J#~'o,}/P8$$$$44 laNytu5v=v?vvvv-w$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50-w.w6www;--- $7$8$H$Ifgd50kdX$$IflִJ#o,}/P8    44 laNytwwx5x7x8x $7$8$H$Ifgd50$$7$8$H$Ifa$gd508x9xAxxx;--- $7$8$H$Ifgd50kdB$$IflִJ#o,}/P8    44 laNytxxxxxxx $7$8$H$Ifgd50$$7$8$H$Ifa$gd50xxx( $7$8$H$Ifgd50kd,$$IflF J#~'o,}/P8$$$$44 laNytx`yhyjylynyoyqyry$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50rysyy( $7$8$H$Ifgd50kd$$$IflF J#~'o,}/P8$$$$44 laNytyyyyyyyyyyyyyyyyyyyW{_{a{c{FfMFf $7$8$H$Ifgd50$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50y_{a{i{j{r{{{{{{{||||||| }"}*}+}3}8}>}}}}}}}}}}-~.~0~5~6~>~U~W~X~~~*+Ł$8'h}B*CJOJPJQJ^JaJph-h}5B*CJOJPJQJ\^JaJph hDA0h503h50h505B*CJOJPJQJ\^JaJph-h50h50B*CJOJPJQJ^JaJph=c{e{f{h{i{ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50i{j{r{( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNytr{{{{{{{{{$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50{{{( $7$8$H$Ifgd50kd$$IflF J#~'o,}/P8$$$$44 laNyt{z||||||||$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50|||( $7$8$H$Ifgd50kd|$$IflF J#~'o,}/P8$$$$44 laNyt|} }"}$}&}'})}*}$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50*}+}3}( $7$8$H$Ifgd50kdt$$IflF J#~'o,}/P8$$$$44 laNyt3}}}}}}}}}$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50}}}( $7$8$H$Ifgd50kdl$$IflF J#~'o,}/P8$$$$44 laNyt}}}}}}}}}-~.~0~1~2~3~4~5~6~>~~~~FfFf $7$8$H$Ifgd50$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50~*$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 $7$8$H$Ifgd};---- $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNyt $7$8$H$Ifgd50$$7$8$H$Ifa$gd50$;--- $7$8$H$Ifgd50kd$$Ifl ִJ#o,}/P8    44 laNyt8XYhiӄ Ј׈׉؉%&(-.6JÊ[rPQYoڌ܌čō΍SU[\e'h'pB*CJOJPJQJ^JaJph'h}B*CJOJPJQJ^JaJph hDA0h503h50h505B*CJOJPJQJ\^JaJph-h50h50B*CJOJPJQJ^JaJph> $7$8$H$Ifgd50$$7$8$H$Ifa$gd50;--- $7$8$H$Ifgd50kd~$$IflִJ#o,}/P8    44 laNytX $7$8$H$Ifgd} $7$8$H$Ifgd50$$7$8$H$Ifa$gd50;--- $7$8$H$Ifgd50kdL$$IflִJ#o,}/P8    44 laNyt$ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50 y;--- $7$8$H$Ifgd50kd$$IflBִJ#o,}/P8    44 laNytԉ։׉ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50׉؉%&;-$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNyt&()*+,-.6MOPFf= $7$8$H$Ifgd50$$7$8$H$Ifa$gd50PQYҌڌ;--- $7$8$H$Ifgd50kd|$$Ifl ִJ#o,}/P8    44 laNytڌ܌NÍč $7$8$H$Ifgd50$$7$8$H$Ifa$gd50čō΍JS;--- $7$8$H$Ifgd50kdX$$IflִJ#o,}/P8    44 laNytSU $7$8$H$Ifgd50$$7$8$H$Ifa$gd50~;--- $7$8$H$Ifgd50kd&$$IflDִJ#o,}/P8    44 laNytƏXZ[ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50[\eؐ;--- $7$8$H$Ifgd50kd$$IflUִJ#o,}/P8    44 laNytex^_rtޑߑMO"#,?"#,9efo̕Εuvce&)*FGκκκκγκγγγγκκΜκκγγ-h50h'pB*CJOJPJQJ^JaJph hDA0h50'h'pB*CJOJPJQJ^JaJph-h50h50B*CJOJPJQJ^JaJph3h50h505B*CJOJPJQJ\^JaJph=c $7$8$H$Ifgd50$$7$8$H$Ifa$gd50DM;--- $7$8$H$Ifgd50kd$$Ifl3ִJ#o,}/P8    44 laNytMO!" $7$8$H$Ifgd50$$7$8$H$Ifa$gd50"#,;--- $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNyt!" $7$8$H$Ifgd50$$7$8$H$Ifa$gd50"#,Ҕܔ;---- $7$8$H$Ifgd50kd^$$IflִJ#o,}/P8    44 laNytbde $7$8$H$Ifgd50$$7$8$H$Ifa$gd50efoÕ̕;--- $7$8$H$Ifgd50kd,$$IflִJ#o,}/P8    44 laNyt̕Ε&rtu $7$8$H$Ifgd50$$7$8$H$Ifa$gd50uvZc;--- $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNytceF $7$8$H$Ifgd50$$7$8$H$Ifa$gd50;-$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50kd$$Ifli ִJ#o,}/P8    44 laNytgprSWX $7$8$H$IfgdFf $7$8$H$Ifgd50$$7$8$H$Ifa$gd50prXYbq &F.&7۞ܞ@BCDؠ٠fhiݡޡqsyzγγγγγγ'hB*CJOJPJQJ^JaJph hDA0h50-h50h50B*CJOJPJQJ^JaJph3h50h505B*CJOJPJQJ\^JaJphFXYb՛ߛ;---- $7$8$H$Ifgd50kd\$$IflִJ#o,}/P8    44 laNyt  $$7$8$H$Ifa$gd50 $7$8$H$Ifgd50;--- $7$8$H$Ifgd50kd8$$IflִJ#o,}/P8    44 laNyt۝ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50&;--- $7$8$H$Ifgd50kd$$Ifl^ִJ#o,}/P8    44 laNyt؞ڞ۞ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50۞ܞ7@;--- $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNyt@BC $7$8$H$Ifgd50$$7$8$H$Ifa$gd50;--- $7$8$H$Ifgd50kd$$IflyִJ#o,}/P8    44 laNytՠנؠ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50ؠ٠]f;--- $7$8$H$Ifgd50kdp$$IflִJ#o,}/P8    44 laNytfhڡܡݡ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50ݡޡhq;--- $7$8$H$Ifgd50kd>$$IflcִJ#o,}/P8    44 laNytqstuvxy $7$8$H$Ifgd50$$7$8$H$Ifa$gd50yz( $7$8$H$Ifgd50kd $$Ifl J#~'o,}/P8$$$$44 laNyt$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 ;--- $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNyt ,_ab(01:PRdĨ&(wy 0|~ګ۫%'FGOZCDLaγ'hB*CJOJPJQJ^JaJph hDA0h503h50h505B*CJOJPJQJ\^JaJph-h50h50B*CJOJPJQJ^JaJphF  $7$8$H$Ifgd50$$7$8$H$Ifa$gd50( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNytV_a$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50;--- $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNyt-/0 $7$8$H$Ifgd50$$7$8$H$Ifa$gd5001:;--- $7$8$H$Ifgd50kd`$$Ifl(ִJ#o,}/P8    44 laNytR $7$8$H$Ifgd50$$7$8$H$Ifa$gd50;--- $7$8$H$Ifgd50kdJ$$IflִJ#o,}/P8    44 laNytZ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50&;--- $7$8$H$Ifgd50kd&$$IflִJ#o,}/P8    44 laNyt&(q $7$8$H$Ifgd50$$7$8$H$Ifa$gd50nw;--- $7$8$H$Ifgd50kd$$IflCִJ#o,}/P8    44 laNytwy $7$8$H$Ifgd50$$7$8$H$Ifa$gd50 ;-$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNytt|~׫٫ګFfA $7$8$H$Ifgd50$$7$8$H$Ifa$gd50ګ۫  ;---- $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNyt%'CEF$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50FGO;--- $7$8$H$Ifgd50kd\ $$IflִJ#o,}/P8    44 laNyt@BC $7$8$H$Ifgd50$$7$8$H$Ifa$gd50CDL;--- $7$8$H$Ifgd50kd* $$Ifl>ִJ#o,}/P8    44 laNyta _`hy{ݱFG³dzȳг"$ VW_rlmu̸θhiqڹܹWXrsuz{HL'hB*CJOJPJQJ^JaJph hDA0h503h50h505B*CJOJPJQJ\^JaJph-h50h50B*CJOJPJQJ^JaJphE \^_ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50_`h;--- $7$8$H$Ifgd50kd $$IfltִJ#o,}/P8    44 laNyt $7$8$H$Ifgd50$$7$8$H$Ifa$gd50;-$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50kd $$IflִJ#o,}/P8    44 laNyt³óijųƳdzȳг"$]}Ff $7$8$H$Ifgd50$$7$8$H$Ifa$gd50;--- $7$8$H$Ifgd50kdZ$$Ifl2ִJ#o,}/P8    44 laNytM $7$8$H$Ifgd^ $7$8$H$Ifgd50$$7$8$H$Ifa$gd50{;--- $7$8$H$Ifgd50kd6$$Ifl) ִJ#o,}/P8    44 laNytSUV $7$8$H$Ifgd50$$7$8$H$Ifa$gd50VW_;--- $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNyt2ikl $7$8$H$Ifgd50$$7$8$H$Ifa$gd50lmuĸ̸;--- $7$8$H$Ifgd50kd$$Ifl^ִJ#o,}/P8    44 laNyt̸θegh $7$8$H$Ifgd50$$7$8$H$Ifa$gd50hiqѹҹڹ;---- $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNytڹܹTVW $7$8$H$Ifgd50$$7$8$H$Ifa$gd50WXrs;-$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50kdn$$Ifl}ִJ#o,}/P8    44 laNytsuvwxyz{BHLaFf$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50$$7$8$H$Ifa$gd50abhwhj;02<=CIؿܿ  W[ !';Z\giqrx017;ԳԳԳԳԳԳԳԳԳԳԳԳͳԳԳԳԳԳԳԳԳԳ3h50h505B*CJOJPJQJ\^JaJph hDA0h50-h50h50B*CJOJPJQJ^JaJph'hm0B*CJOJPJQJ^JaJphFabhbh;--- $7$8$H$Ifgd50kd$$IflִJ#o,}/P8    44 laNythjlnoq $7$8$H$Ifgd50$$7$8$H$Ifa$gd50( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNyt   $$7$8$H$Ifa$gd50 $7$8$H$Ifgd50( $7$8$H$Ifgd50kd$$Ifl J#~'o,}/P8$$$$44 laNyt)02489;<$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50<=C( $7$8$H$Ifgd50kd$$IflF J#~'o,}/P8$$$$44 laNytCؿ:Q$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50 ;--- $7$8$H$Ifgd50kd$$IflcִJ#o,}/P8    44 laNyt  W  $7$8$H$Ifgd50$$7$8$H$Ifa$gd50 !';--- $7$8$H$Ifgd50kd$$IflDִJ#o,}/P8    44 laNyt $7$8$H$Ifgd50$$7$8$H$Ifa$gd50( $7$8$H$Ifgd50kd$$IflF J#~'o,}/P8$$$$44 laNytTZ\^`acFf! $7$8$H$Ifgd50$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50( $7$8$H$Ifgd50kdX#$$Ifly J#~'o,}/P8$$$$44 laNytagikmnpq$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50qrx( $7$8$H$Ifgd50kdP$$$Ifl J#~'o,}/P8$$$$44 laNytx0$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50017( $7$8$H$Ifgd50kdH%$$Ifl J#~'o,}/P8$$$$44 laNyt7$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50;<BI&'(018;E45679:<=?@BCDEFG^_jhgOTh/ CJUhgOThcNCJ hcNCJhjhU h,t_hY433h50h505B*CJOJPJQJ\^JaJph hDA0h50-h50h50B*CJOJPJQJ^JaJph:( $7$8$H$Ifgd50kd2&$$Ifl J#~'o,}/P8$$$$44 laNyt;$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50;<B( $7$8$H$Ifgd50kd'$$Ifl J#~'o,}/P8$$$$44 laNytB$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50( $7$8$H$Ifgd50kd'$$Ifl J#~'o,}/P8$$$$44 laNyt $$7$8$H$Ifa$gd50 $7$8$H$Ifgd50($$7$8$H$Ifa$gd50kd($$Ifl J#~'o,}/P8$$$$44 laNyt !"#$%&$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50&'(($$7$8$H$Ifa$gd50kd)$$Ifl J#~'o,}/P8$$$$44 laNyt()*+,-./0$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50018( $7$8$H$Ifgd50kd*$$Ifl J#~'o,}/P8$$$$44 laNyt8$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50;* $7$8$H$Ifgd50$$7$8$H$Ifa$gd50kdZ+$$IflִJ#~'o,}/P8    44 laNytRD $7$8$H$Ifgd50kd ,$$Iflr~'o,}/P8$44 laNyt$$7$8$H$Ifa$gd50$$7$8$H$Ifa$gd501234}$$7$8$H$Ifa$gd50 $7$8$H$Ifgd50$$7$8$H$Ifa$gd50Qkd,$$Ifl0P8544 laNyt45689;<>?ABDtojhjhjhjhf$gdgOTgd:wkd,$$IflFr~'o,}/P8$44 laNyt DEcdefgd:w$_abcef h,t_hY43hhgOThcNCJjhgOTh/ CJU*h CJmHnHu*5 01h:pR@/ =!"#$% ?0P1h:p]// =!"#$% Dp21h:p;o/ =!"#$% 51h0:p.1i= /!"#$% 51h0:p[)= /!"#$% B$$If!vh#vh%:V l@ t65TV$$If!vh#vh%:V l t6,5/ OTH$$If!vh#vh%:V lh t6,5T}DyK _Toc225746170}DyK _Toc225746171}DyK _Toc225746172}DyK _Toc225746173}DyK _Toc225746174}DyK _Toc225746175}DyK _Toc225746176}DyK _Toc225746177}DyK _Toc225746178}DyK _Toc225746179}DyK _Toc225746180}DyK _Toc225746181}DyK _Toc225746182}DyK _Toc225746183}DyK _Toc225746184}DyK _Toc225746185}DyK _Toc225746186}DyK _Toc225746187}DyK _Toc225746188}DyK _Toc225746189}DyK _Toc225746190IDyK yK http://www.nlm.nih.gov/digitalrepository/NLM Digital Repository Requirements rev March 2007.pdfyX;H,]ą'c$$If!vh#v9 #v8#vF#vs:V  t06,5 55(5F34Byt4$$If!vh#v9 #v8#vF#vs:V  t06,5 55(5F34Byt4$$If!vh#v9 #v8#vF#vs:V  t06,5 55(5F34Byt4$$If!vh#v9 #v8#vF#vs:V  t06,5 55(5F34Byt4$$If!vh#v9 #v8#vF#vs:V  t06,5 55(5F34Byt4$$If!vh#v9 #v8#vF#vs:V  t06,5 55(5F34Byt4DyK yK nhttp://www.nlm.nih.gov/exhibition/cholera/yX;H,]ą'c DyK yK http://www.nlm.nih.gov/exhibition/historicalanatomies/home.htmlyX;H,]ą'cDyK yK http://www.nlm.nih.gov/exhibition/historicalanatomies/vesalius_home.htmlyX;H,]ą'cDyK yK http://www.nlm.nih.gov/exhibition/historicalanatomies/albinus_home.htmlyX;H,]ą'cDyK yK hhttp://intramural.nih.gov/mainpage.htmlyX;H,]ą'c}$$If!vh#vF#vT#v#v #vp#v#v :V d44 Fb45F5T55 5p55 / / / / 4 daf4pFyto{kd$$Ifd44֞Z l#*4FT p  Fb444 daf4pFyto{$$If!vh#vF#vT#v#v #vp#v#v :V d4b4+5F5T55 5p55 /  / / 4 daf4yto{$$If!vh#vF#vT#v#v #vp#v#v :V d4b4+5F5T55 5p55 /  / / 4 daf4yto{$$If!vh#vF#vT#v#v #vp#v#v :V d4b4+5F5T55 5p55 /  / / /  4 daf4yto{$$If!vh#vF#vT#v#v #vp#v#v :V d4b4+5F5T55 5p55 /  / / / 4 daf4yto{$$If!vh#vF#vT#v#v #vp#v#v :V d4b4+5F5T55 5p55 /  / / 4 daf4yto{$$If!vh#vF#vT#v#v #vp#v#v :V d4b4+5F5T55 5p55 /  / / /  4 daf4yto{$$If!vh#vF#vT#v#v #vp#v#v :V d4b4+5F5T55 5p55 /  / / / 4 daf4yto{$$If!vh#vF#vT#v#v #vp#v#v :V d4b4+5F5T55 5p55 / / / / 4 daf4yto{$$If!vh#vF#vT#v#v #vp#v#v :V d4b4+5F5T55 5p55 / / / / 4 daf4yto{$$If!vh#vF#vT#v#v #vp#v#v :V d4b4+5F5T55 5p55 / / / / 4 daf4yto{$$If!vh#v#v>#v#v[#v%:V lKb455>55[5%/ /  / / / /  / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / / / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V l b4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lZb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l b4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lWb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l`b4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lWb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l b4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l b4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ /  / / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l? <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l0b4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lcb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ /  / / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lHb4555>55, 5/5%/ / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l3b4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ /  / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ / ap<yt !$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ ap<yt !$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ ap<yt !$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ ap<yt !$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ ap<yt !$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ ap<yt !$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ ap<yt !$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ ap<yt !$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ ap<yt !$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ ap<yt !$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ ap<yt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/  / ap<yt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lHb4555>55, 5/5%/ / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lHb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lHb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lHb4555>55, 5/5%/ /  / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lHb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l6b4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l b4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ /  / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ /  / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ /  / / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l b4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l b4555>55, 5/5%/ /  / / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V l?b4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ /  / / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lcb4555>55, 5/5%/ / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lcb4555>55, 5/5%/ /  / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l`b4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lWb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ /  / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l0b4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l<b4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V l'b4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ /  / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lob4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ /  / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l3 <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lWb4555>55, 5/5%/ / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ /  / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V lwb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lHb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lHb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ /  / / / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v#v>#v#v, #v/#v%:V l=b4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ / / / / ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/ ayt $$If!vh#v#v#v#v, #v/#v%:V lb45555, 5/5%/ ayt x$$If!vh#v#v(#v/#v%:V lb455(5/5%/ ayt \$$If!vh#v#vQ0:V lb455Q0/ ayt x$$If!vh#v#v(#v/#v%:V lb455(5/5%/ ayt $$If!vh#v#v#v>#v#v, #v/#v%:V lb4555>55, 5/5%/  / ayt /$$If!vh#v#v>#v#v, #v/#v%:V l <b455>55, 5/5%/ /  ap<yt $$If!vh#v#v(#v/#v%:V lb455(5/5%/ / ayt $$If!vh#v#v#v#v, #v/#v%:V lb45555, 5/5%/ ayt x$$If!vh#v#v(#v/#v%:V lb455(5/5%/ ayt $$If!vh#v#v#v#v, #v/#v%:V lb45555, 5/5%/ ayt \$$If!vh#v#vQ0:V lb455Q0/ ayt \$$If!vh#v#vQ0:V lwb455Q0/ ayt \$$If!vh#v#vQ0:V lb455Q0/ ayt $$IfN!vh#v#v#v#vN #v2#v:V l*5555N 525/ /  / / /  / /  / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lw5M5555N 525/ / / / / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lj 5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l.5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lZ5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lH5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lH5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lW5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #vD :V ln5M5555N 5D / / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ /  / / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l? <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l*5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lw5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ /  / / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lH5M5555N 525/ / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l(5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ /  / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ / aNp<ytp!$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ aNp<ytp!$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ aNp<ytp!$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ aNp<ytp!$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ aNp<ytp!$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ aNp<ytp!$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ aNp<ytp!$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ aNp<ytp!$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ aNp<ytp!$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ aNp<ytp!$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ aNp<ytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/  / aNp<ytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lH5M5555N 525/ / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lH5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lw5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l" 5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lw5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lT5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l65M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lc5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l 5M5555N 525/ /  / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l: 5M5555N 525/ / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lH5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lH5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l"5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lw5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lw5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lc5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lc5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ /  / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lw5M5555N 525/ / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lH5M5555N 525/ /  / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lw5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ /  / / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lw5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ /  / / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ /  / / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lH5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lw 5M5555N 525/ /  / / aNpytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l`5M5555N 525/ / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ /  / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lH5M5555N 525/ / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l65M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l*5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l"5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ /  / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l 5M5555N 525/ /  / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l3 <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l?5M5555N 525/ / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lQ5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ /  / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lw5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V lH5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #vD :V l5M5555N 5D / / / / / aNytp$$IfN!vh#vM#v#v#v#vN #vD :V l5M5555N 5D / / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ /  / / / aNytp/$$IfN!vh#v#v#v#vN #v2#v:V l <5555N 525/ /  aNp<ytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ / / / / aNytp$$IfN!vh#vM#v#v#v#vN #v2#v:V l5M5555N 525/ aNytp$$IfN!vh#vM#v}#v#vN #v2#v:V l5M5}55N 525/ aNytpx$$IfN!vh#vM#v*#v2#v:V l5M5*525/ aNytp\$$IfN!vh#vM#v4:V l5M54/ aNytpx$$IfN!vh#vM#v*#v2#v:V l5M5*525/ aNytp$$IfN!vh#v#v#v#v:V l5555/  / / / / / aNytJ$$IfN!vh#v#v#v#v#v4#v#v#v:V l555554555/  / / /  / /  / / /  / /  / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l-55555555/ / / / / / / / aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kdH$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lX555555555 / /  /  / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V lX55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l 55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ /  / / / aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kdvX$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lb555555555 / /  /  / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lw555555555 / /  / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V lF55555555/ / / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / /  aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kdd$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lL555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lj555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / /  aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ / aNpPyt=kdl$$IflִJ#~'o,}/P8 P    44 laNpPyti$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ aNpPyt=kdp$$IflִJ#~'o,}/P8 P    44 laNpPyti$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ aNpPyt=kd>t$$IflִJ#~'o,}/P8 P    44 laNpPyti$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ aNpPyt=kdw$$IflִJ#~'o,}/P8 P    44 laNpPyti$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ aNpPyt=kd{$$IflִJ#~'o,}/P8 P    44 laNpPyti$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ aNpPyt=kd<$$IflִJ#~'o,}/P8 P    44 laNpPyti$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyti$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyti$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ aNpPyt=kd:$$IflִJ#~'o,}/P8 P    44 laNpPyti$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyti$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/  / aNpPyt=kd8$$IflִJ#~'o,}/P8 P    44 laNpPytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l<555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l2555555555 / /  / /  aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd\$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l 555555555 / /  /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l^555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l$ 555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lS555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l2555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l2555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lb555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / /  aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l 555555555 / /  / /  aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  /  / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / /  aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  /  / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / /  aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  /  / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / /  aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kdd$$IflִJ#~'o,}/P8 P    44 laNpPytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l 55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V lB55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ /  / / aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!vh#v#v#v#v#v#v#v#v:V l 55555555/ / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V lD55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V lU55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l355555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V li 55555555/ /  / / aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l^55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V ly55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V lc55555555/ / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l(55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V lC55555555/ / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ /  / / aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l>55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V lt55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ /  / / aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd $$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!vh#v#v#v#v#v#v#v#v:V l255555555/ / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l) 55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l^55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l}55555555/ /  / / aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kdJ$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ / / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V lc55555555/ / / / / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V lD55555555/ / / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V lF555555555 / /  / / /  aNytw$$IfN!vh#v#v#v#v#v#v#v#v:V l P55555555/ /  aNpPyt=kd$$IflִJ#~'o,}/P8 P    44 laNpPyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V ly555555555 / /  /  / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / /  / / / aNyt$$IfN!v h#v#v#v#v#v#v#v#v#v :V l555555555 / aNyt$$IfN!vh#v#v#v#v#v#v#v#v:V l55555555/ aNyt$$IfN!vh#v#v$#v#v#v:V l55$555/ aNyt\$$IfN!vh#v#v5:V l555/ aNyt$$IfN!vh#v#v$#v#v#v:V lF55$555/ aNyt^0 666666666vvvvvvvvv666666>666666666666666666666666666666666666666666666666hH6666666666666666666666666666666666666666666666666666666666666666662 0@P`p2( 0@P`p 0@P`p 0@P`p 0@P`p 0@P`p 0@P`p8XV~_HmH nH sH tH D`D  mNormalCJPJ_HaJmH sH tH V@V :w Heading 1dd@&[$\$5CJ$KH$PJ\aJ(J@J '7 Heading 2$$@&5CJ\aJT@T JX Heading 3$$@&5B*OJQJ\phON@N JX Heading 5$$@&B*OJQJph$?`DA D Default Paragraph FontRi@R 0 Table Normal4 l4a (k ( 0No List J^@J  m0 Normal (Web)dd[$\$OJQJBOB mbodytextdd[$\$OJQJDOD m stepfielddd[$\$OJQJxO"x mpanelKM NOPQ]^OJQJ~O2~ m notemacroIddM NOPQ[$\$OJQJOB m warningmacroIddM NOPQ[$\$OJQJ~OR~ m infomacroIddM N*B*phH@H ,t_0 Balloon TextCJOJQJ^JaJRoR ,t_0Balloon Text CharCJOJPJQJ^JaJ  /pnobr@B@@ !o{ Body Text 7$8$H$PJaJ8o8 o{Body Text CharCJ4"4 #gOT0Header "H$:o1: "gOT0 Header Char CJPJaJ4 @B4 %gOT0Footer $H$:oQ: $gOT0 Footer Char CJPJaJ.X`a. 4@Emphasis6]JoqJ 7Heading 2 Char5CJPJ\^JaJr Ar ]/p TOC Heading($$d@& [$\$!B*CJKHOJPJQJaJph6_6@6 ]/pTOC 1)d$ T`T +]/ No Spacing*$CJOJPJQJ_HaJmH sH tH ^o^ *]/No Spacing Char(CJOJPJQJ^J_HaJmH sH tH FV`F 4Q0FollowedHyperlink >*B* ph.@. ckpTOC 2 -d^HY@H /DA00 Document Map.CJOJQJ^JaJRoR .DA00Document Map CharCJOJPJQJ^JaJPK![Content_Types].xmlN0EH-J@%ǎǢ|ș$زULTB l,3;rØJB+$G]7O٭V$ !)O^rC$y@/yH*񄴽)޵߻UDb`}"qۋJחX^)I`nEp)liV[]1M<OP6r=zgbIguSebORD۫qu gZo~ٺlAplxpT0+[}`jzAV2Fi@qv֬5\|ʜ̭NleXdsjcs7f W+Ն7`g ȘJj|h(KD- dXiJ؇(x$( :;˹! I_TS 1?E??ZBΪmU/?~xY'y5g&΋/ɋ>GMGeD3Vq%'#q$8K)fw9:ĵ x}rxwr:\TZaG*y8IjbRc|XŻǿI u3KGnD1NIBs RuK>V.EL+M2#'fi ~V vl{u8zH *:(W☕ ~JTe\O*tHGHY}KNP*ݾ˦TѼ9/#A7qZ$*c?qUnwN%Oi4 =3N)cbJ uV4(Tn 7_?m-ٛ{UBwznʜ"Z xJZp; {/<P;,)''KQk5qpN8KGbe Sd̛\17 pa>SR! 3K4'+rzQ TTIIvt]Kc⫲K#v5+|D~O@%\w_nN[L9KqgVhn R!y+Un;*&/HrT >>\ t=.Tġ S; Z~!P9giCڧ!# B,;X=ۻ,I2UWV9$lk=Aj;{AP79|s*Y;̠[MCۿhf]o{oY=1kyVV5E8Vk+֜\80X4D)!!?*|fv u"xA@T_q64)kڬuV7 t '%;i9s9x,ڎ-45xd8?ǘd/Y|t &LILJ`& -Gt/PK! ѐ'theme/theme/_rels/themeManager.xml.relsM 0wooӺ&݈Э5 6?$Q ,.aic21h:qm@RN;d`o7gK(M&$R(.1r'JЊT8V"AȻHu}|$b{P8g/]QAsم(#L[PK-![Content_Types].xmlPK-!֧6 0_rels/.relsPK-!kytheme/theme/themeManager.xmlPK-!0C)theme/theme/theme1.xmlPK-! ѐ' theme/theme/_rels/themeManager.xml.relsPK] xf 7 x    .....................1N 8eyy&5?;IZN:Wl~Ǘs(]8! .d5BpLR[dlt|1Xt:+TM0 -=E>L(Yse#ry8ea_fehijlmnopqsuy{(8K`r(EZl,9Pex&8M_V 916:4>BtMMM N5NYN$PV_hvtR?<Q OQV.%c`  $ G L M    \a S?>CD{5INvwKLBCwxj.5 )   !!U"W#($$u%%%&&( ))J*e*+8+++h,o,-- ....//Q00X112233T4[4a55:7;=<=> ??"?#??@@AAA BBBkCCC0D1DDxE}EFFQHHJJJJJJtLLLM%N*NNNNN,O-OKPVQRRRUS5TTUUUUUVJWWkXX)YGYYZ [[[h\+]]/^z^j__=`B`C`aLbCcccdddeff)g.g hvh{h;iijjjkll,mmmmmnooPppbqrrrrrrsKtxtuvuvUvvv^wwwwwxyy8zIzzzI{{4|||}}~~G &*008XZ[:%Չ IOP(TV)IMioڞߞs../4FMЧ.kpq4589ghٮڮ XYįů9:wx±1Hn'.˹~AFGY8n9aSr!.)V,6I8k  %&u:;PU;ptu6;sx 49:z{EvVZ5tg_Usc}zNEBmr3"%fP.<AB. S0^k|  \  9   t      49.=tyzzty#(|?*hq"#Y$Y%%&T'q(( )+-m-w-/|012344455799:::;;<=.=7=> >>>@@9ABACCD DhDDDEaFFGIHOHHINIJJKK8L>L(M.MMMOO`PgPQQSSMUSUVV'Y-YYYZZb[h[]]Q^X^(_/_``abbb.d5dreyeffiiejlj,l?l(n.nqqrrssZtcttuuu-ww8xxxxryyc{i{r{{{||*}3}}}~׉&PڌčS[M""e̕ucX۞@ؠfݡqy 0&wګFC_Vl̸hڹWsah<C  qx07;B&(084Dffgkrtvwxz|}~      !"#$%&')*+,-./012345679:;<=>?@ABCDEFGHIJLMNOPQRSTUVWXYZ[\]^_abcdefghijklmnopqstuvwxyz{|}~      !"#$%&')*+,-./0123456789:;<=>?@ABCDFGHIJKLMNOPQRSTUVWXY[\]^_`abcdefghijkmnopqrstuvwxyz{|}~      !"#$%&'()*+-./012345678:;<=>?@ABCDEFGHIJKLMNOQRSTUVWXYZ[\]^_`abcdfghijklmnopqrstuvwyz{|}~      !"#$%'()*+,-./012345679:;<=>?@ABCDEFGHIJKLNOPQRSTUVWXYZ[\]^ ;=>@_3OQRTs %'(*Iz   .[wyz|%ACDFey:^z}~9<=?^Eadeg / 2 3 5 T y +???ڹ2Hdf X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%X%̕XXXXXX (+1!L# @0(  B S  ?3 _Toc225746170 _Toc225746171(IntroductionandWorkingGuidelines-2.1.Int _Toc225746172(IntroductionandWorkingGuidelines-2.2.Wor _Toc225746173(IntroductionandWorkingGuidelines-2.2.1.G(IntroductionandWorkingGuidelines-2.2.2.R _Toc225746174(MethodologyandInitialSoftwareEvaluationR _Toc225746175 _Toc225746176 _Toc225746177(3.2.Phase1-QualitativeEvaluation-Archiva(3.2.Phase1-QualitativeEvaluation-CONTENT'3.2.Phase1-QualitativeEvaluation-DAITSS(3.2.Phase1-QualitativeEvaluation-DigiToo'3.2.Phase1-QualitativeEvaluation-DSpace(3.2.Phase1-QualitativeEvaluation-EPrints'3.2.Phase1-QualitativeEvaluation-Fedora(3.2.Phase1-QualitativeEvaluation-Greenst(3.2.Phase1-QualitativeEvaluation-Keyston&3.2.Phase1-QualitativeEvaluation-VITAL _Toc225746178 _Toc225746179(SummaryofHands-onEvaluation-4.1Summaryof _Toc225746180 _Toc225746181(RecommendationtouseFedoraandConductaPhas _Toc225746182 _Toc225746183(Phase1PilotRecommendations-5.2.1.Compani(Phase1PilotRecommendations-5.2.2.Workflo(Phase1PilotRecommendations-5.2.3.Suggest&Phase1PilotRecommendations-68months%3A'Phase1PilotRecommendations-818months%3A(Phase1PilotRecommendations-5.2.4.NLM%27s _Toc225746184#Phase1PilotResourcesNeeded-5.3.1.LO%Phase1PilotResourcesNeeded-5.3.2.OCCS _Toc225746185(PilotCollections-5.4.1.CholeraMonographs(PilotCollections-5.4.2.DigitizedMotionPi(PilotCollections-5.4.3.ImageFilesfromHis(PilotCollections-5.4.4.NIHInstituteAnnua _Toc225746186 _Toc225746187 _Toc127263422 _Toc225746188 _Toc225746189 _Toc225746190 ''cc{"=#=#|#[&'k,-6. 013~4)69: <BPEPEǏ#?sΫDzlx)g  !"#$%&'()*+,-./012 &'8cz{"{##[&&'k,-6. 013~4)69:7<BPErEƏ#?s ΫDzl?Ng$$gg9*urn:schemas-microsoft-com:office:smarttagsplaceB*urn:schemas-microsoft-com:office:smarttagscountry-region   ?~ LR\c4 > ++++k,w,-- 00#0)01133338<><@<H<<>B>T>[>@@@@[AaAuA{AAA~EEEEaFgFEGOGGGGGHHHHI!III>MGMzNNNOTOOO%P/PPPPP5Q;QQQRRRRRRSSSS}TTTTVVIXPXYYYY]]__ _$___4a:aaa4bѡ١SZ[c*0-2rx S\@I  Y _ 09NT4=/)7)W/_/112222L4R4445566>>AAOOQQ"R+RSSYTbTYZZZ [[__aayc}ccciiiiHnNnjupuuuvvv1vNvYvNxUxxx}}~"~~ހ6>ȁ>HuzǬ٬&.[`NSYa̷ѷӷ۷emglny ov,1;Cae)/ `i/6jr%-NVpy     .3# #D#N###%%((****$,.,,,@@BBBBVC`CCCDD+K5KM M-O8OyOO/P:PPPX$XeXpXXXYYYY\\eegghhiioo-y8yzz#|-|X|^| -86>0:@JDKDNu(3޹BI689;<>?ABdg?  / 'M'CCkkpIqCM¦ah689;<>?ABdg56Fbg? 689;<>?AFbg:9XPj"BOZ <>nbD (nJG8w/Gs|j@BT]AFĔ s|`xFP`L>x1uB$gnCSN* 6;1 !^Eg)+2)tb}*<{V,@@x3Q0S5[56WD?@7-S7#D08tS:;};m2<>sg|=&)V?L/*h@[A|NDB1ELl>ݒuam&xn5n&ސEMxT8yV^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo( ^`OJQJo( pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo(^`OJPJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo(^`OJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo(^`OJPJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo(^`OJPJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo(^`OJQJ^Jo(o pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo(^`OJPJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo(^`OJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o( ^`OJQJo(^`OJPJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo(^`OJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo(^`OJPJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo(^`OJPJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o( ^`OJQJo(^`OJPJQJ^Jo(" pp^p`OJ QJ o( @ @ ^@ `OJQJo(^`OJQJ^Jo(o ^`OJ QJ o( ^`OJQJo(^`OJQJ^Jo(o PP^P`OJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(^`CJOJQJo(^`CJOJQJo(opp^p`CJOJ QJ o(@ @ ^@ `CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(^`CJOJ QJ o(PP^P`CJOJ QJ o(:5nS5`9f 41TWM_1 !"y]FADBj" _D089BAF!/KxnSV,ELl+2);};S:2<x3ybD sOZ uspgf[!=Ram8w/LI)V? CC&C_LCtG%cJ LhL\NcNpN?O[QwQ{QiRgOTYVCW9\%]x/^]l^_,t_`g`+aF~bh'e/#f.g<(g.1i ]i"jckc~k'l;oFo#'sbuz%+~2E'p|?Hq/Hc)-/pG9]kac4R6&JXncd R `5D]/Z50H<[@]\htZ^s~e2<Nkr4# XnzdG RF._pHkm >=oz?5t:w( _~v^U Z24Q7}6SXR@s y68@ f@Unknown G* Times New Roman5Symbol3. * Arial7@Cambria7.@ CalibriWSimSunArial Unicode MS7.  Verdana5. *aTahoma?= * Courier New;WingdingsA$BCambria Math"1h2g2g fDiXIhDiXIh!x0BHX  $Pn2:! xx 5Recommendations on NLM Digital Repository Software Diane Boehr, Brooke Dine, John Doyle, Laurie Duquette, Jenny Heiland, Felix Kong, Kathy Kwan, Edward Luczak, Jennifer Marill (chair), Michael North, Deborah Ozga and John Rees. Doron Shalvidine:                           ! " # $ % & ' ( ) * + , - . / 0 1 2 3 4 5 6 7 8 9 Oh+'0l   ( 4 @LT\d8Recommendations on NLM Digital Repository Software Diane Boehr, Brooke Dine, John Doyle, Laurie Duquette, Jenny Heiland, Felix Kong, Kathy Kwan, Edward Luczak, Jennifer Marill (chair), Michael North, Deborah Ozga and John Rees. Doron Shalvi Normal.dotmdine2Microsoft Office Word@@vd@,C@,CIDiX՜.+,D՜.+,|8 hp   National Library of Medicineh 6Recommendations on NLM Digital Repository Software Title (V^_PID_LINKBASE _PID_HLINKSAFhttp://wiki.nlm.nih.gov/confluenceA 8d(http://intramural.nih.gov/mainpage.html"Hhttp://www.nlm.nih.gov/exhibition/historicalanatomies/albinus_home.html/Ihttp://www.nlm.nih.gov/exhibition/historicalanatomies/vesalius_home.html<6@http://www.nlm.nih.gov/exhibition/historicalanatomies/home.htmlb=+http://www.nlm.nih.gov/exhibition/cholera/z7`http://www.nlm.nih.gov/digitalrepository/NLM Digital Repository Requirements rev March 2007.pdf2z_Toc2257461902t_Toc2257461892n_Toc2257461882h_Toc2257461872b_Toc2257461862\_Toc2257461852V_Toc2257461842P_Toc2257461832J_Toc2257461822D_Toc2257461812>_Toc22574618028_Toc22574617922_Toc2257461782,_Toc2257461772&_Toc2257461762 _Toc2257461752_Toc2257461742_Toc2257461732_Toc2257461722_Toc2257461712_Toc225746170  !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`bcdefghijklmnopqrstuvwxyz{|}~      !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwyz{|}~      #$Root Entry F;C"Data az-1Tablex WordDocument  SummaryInformation(DocumentSummaryInformation8MsoDataStore@C1CGVXG3LPP==2 @C (CItem  PropertiesJKJVCDTOW1==2 @C1CItem  PropertiesUCompObjr 2008-11-24T00:00:00   F Microsoft Word 97-2003 Document MSWordDocWord.Document.89q