Popular in Team Process Product
verified elite notetaker
Popular in 324
This 4 page Bundle was uploaded by Nishtha on Wednesday May 18, 2016. The Bundle belongs to INFO at Drexel University taught by Jennifer Booker in Spring 2016. Since its upload, it has received 10 views. For similar materials see Team Process Product in 324 at Drexel University.
Reviews for OPOW critique
Report this Material
What is Karma?
Karma is the currency of StudySoup.
You can buy or earn more Karma at anytime and redeem it for class notes, study guides, flashcards, and more!
Date Created: 05/18/16
OPOW – OAIPMH Output Writer Software Requirements Specification 1 Introduction 1.1 Document Purpose This document is the System Requirements Specification for OPOW, the OAIPMH Output Writer. 1.2 OPOW Overview OPOW is a file reformatting program that reads a plain text input file in one format, converts the input to an XML format, and writes the reformatted data to an output file. It reads a file of metadata about educational resources drawn from one or more repositories. The program reformats the input data and outputs it as an XML document that meets the OAIPMH standard. The resulting XML document can be made available on the Web and harvested by Service Providers that can then provide searching of the educational resources. Figure 1 shows this context for OPOW. In the figure, metadata for two repositories has been put into a metadata file. OPOW reads this file and outputs an XML file formatted according to the OAIPMH standard. At some later, unspecified time, the XML file can be harvested by a service provider. Repo Service Metadata OPOW OAIPMH Provider Repo Figure 1 Overview of OPOW processing OPOW is being developed as part of the NSFfunded Ensemble project. Ensemble is building a distributed digital library of education materials for computing educators. In terms of the diagram above, Ensemble is a service provider. Ensemble will harvest OAI PMH metadata and use that metadata to provide a single place to search many repositories of computing education materials. OPOW will be one path to connect the repositories to Ensemble. Ensemble can be viewed at http://computingportal.org. The OAIPMH data provided by OPOW will appear in the “Collections” section. 1 1.3 Definitions and Acronyms Dublin Core The Dublin Core metadata format is a standard in the fields of library and computer science. It defines a standard set of terms that can be used to describe library or digital repository contents. The set of metadata elements is similar to the information typically contained in a library catalog to describe a book or periodical. A list of the core elements and definition of them is contained at: http://dublincore.org/documents/usageguide/elements.shtml OAIPMH Open Archives Initiative Protocol for Metadata Harvesting This is a low barrier mechanism for repository interoperability. It involves the methodologies associated with both harvesting and providing metadata about a collection of records. Data Providers are repositories that expose structured metadata via OAIPMH. Service Providers then make OAIPMH service requests to harvest that metadata. The specification can be found at: http://www.openarchives.org/OAI/openarchivesprotocol.html In the context of OPOW, the metadata are elements that describe an educational resource such as a test, an exam, a lecture, or a homework assignment. The metadata elements are the Dublin Core elements. OPOW takes a text file of metadata and converts it to the XML format that OAIPMH specifies a Data Provider should use to expose metadata for harvesting. Repository a collection of digital objects. For OPOW, the repositories contain educational resources. OPOW does not interact with the repositories directly. Resource – an item in a repository. For OPOW, resources are educational materials such as quizzes, tests, lectures, homework assignments, etc. 2 User Characteristics To be complete . 3 Specific Requirements 3.1 External Interface s 3.1.1 Data Interface OPOW will have two data interfaces. Input file The input interface is a plain text file that contains metadata (title, subject, creator, date, etc) describing educational resources (lectures, tests, 2 assignments, etc.) contained in some digital repository. This file may be created by some process outside of OPOW, or created by manual data entry within OPOW. Output file The output interface is an XML file in OAIPMH format. It will be suitable for harvesting by a Service Provider as defined in the OAIPMH context. OPOW produces the file but is not responsible for making the file available for harvesting. 3.1.2 User Interface The user interface of OPOW will provide editing access to the input file and to a set of program options . 3.2 Functions The statements below define the functional requirements for the system. 3.2.1 – Metadata Conversion OPOW will convert a file of metadata into an XML file formatted according to the OAIPMH standard . 3.2.2 – Input File OPOW will read input from a file with the following characteristics : 220.127.116.11 The input file will be plain text 18.104.22.168 The input file will have a layout that is visually easy for a person to read and edit with a text editor 22.214.171.124 The input file consists of metadata that describes educational resources. The metadata for each resource will consist of pairs where each pair will be a metadata term and a value. For example, a pair might be the term “creator” and the value “Smith, Jane”. The metadata terms will be some or all of the Dublin Core terms listed at the Web site referenced in the Dublin Core definition above . 3.2.3 – Data Validatio n OPOW will verify that the input data meets the following criteria and produce an error log for any discrepancies encountere d 126.96.36.199 Any metadat aterm may occur zero or more times for a given resourc e 188.8.131.52 Metadata terms cannot be null 184.108.40.206 Metadata values can be null or any pattern of bytes 220.127.116.11 Files that contain data from more than one repository must provide a repository ID for each resourc e 3 18.104.22.168 Files that contain data from a single repository need not provide a repository ID 22.214.171.124 OPOW will have a user controlled option that will produce a warning message for any metadata term encountered in the input file that is not in the Dublin Core set of term s 126.96.36.199 OPOW will provide a user configuration option to replace or extend the set of metadata terms considered valid by OPOW. The Dublin Core metadata terms will be the default set if none are specified by the user. If the user specifies terms, those should be considered valid by OPOW . 3.2. 4 Output File OPOW will write an output file with the following characteristics: 188.8.131.52 The file will be valid XM L 184.108.40.206 The file content will meet the OAIPMH standard for metadata using Dublin Core elements . 3.2.5 – Configuration Options OPOW will provide a user interface to set configuration options that OPOW will store and apply until changed by the user. These options will be 220.127.116.11 The location and name of the input file 18.104.22.168 The location and name of the output file 3.2.6 – Program Execution 22.214.171.124 OPOW will execute as a standalone program that is started and run as neede d 126.96.36.199 OPOW will be able to execute in silent mode. That is, it can complete execution with no interaction with a person during execution. 188.8.131.52 OPOW will be able to execute in an interactive mode. In this mode, the person interacting with OPOW will be able to edit the input file and configuration options before the input file is processed 3.2.7 – Input File Editin g OPOW will provide a user interface for viewing and editing data in the input file. 184.108.40.206 OPOW will provide an interface for creating a new input fil e 220.127.116.11 OPOW will provide an interface to search and browse the data in the input file. 18.104.22.168 OPOW will provide an interface to add and modify data in the input file. 4
Are you sure you want to buy this material for
You're already Subscribed!
Looks like you've already subscribed to StudySoup, you won't need to purchase another subscription to get this material. To access this material simply click 'View Full Document'