DOC PREVIEW
CORNELL CS 501 - Feasibility2

This preview shows page 1-2-3 out of 10 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 10 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

FEASIBILITY STUDY The Group Douglas Tak-Lai Wong, [email protected] Gregor Charles Carrigan, [email protected] James Ioannidis, [email protected] Jeffery Zhang, [email protected] Talitha Lynn Forcier, [email protected] The Client Bob Kibbee, Map & GIS Librarian, Olin Library, [email protected] The Task to be Undertaken The project is to develop an interactive web-based mapping application to search the complete range of geo-referenced materials in the Cornell University Library. The interactive map would allow a user to find maps through maps, providing a more intuitive interface to cartographic catalog browsing. The project consists of three main parts: determining a database solution to hold the metadata for the library’s map resources, developing an administrative interface that would allow for adding and changing metadata for map holdings, and developing a UI to expose this metadata to the end user (library patrons). Benefits: Currently library patrons have a difficult time locating maps due to the fact that the patron is in a “geographic” mindset and the library catalog requires that they translate their query into an often obscure textual query. 1. The proposed mapping application would allow additional metadata to be appended to current catalog information to aid indexing and searchability. 2. The proposed mapping application would provide a framework for library patrons to visually and intuitively locate paper maps and atlases, digital maps scanned from the collection, and GIS resources; thus overcoming the challenges of the current catalog system and promoting the accessibility of these valuable resources.A Preliminary Requirements Analysis: The system needs to meet the following functional requirements: 1. Web Interface a) Administrator Side i. Allow admin to modify, delete, or add the cartographic information for a particular map ii. Search by region name iii. Display necessary metadata information for a particular map b) Public Side i. Display interactive map 1. Must be able to zoom to at least three levels: world, continent, and country 2. Must provide a minimum level of geographic detail including country boundaries, country names, and a distinction between land and water 3. Must provide both catalog information and possibly some additional metadata on holdings for the current region based on click location and zoom-level 4. Must be able to make several key distinctions between maps, the only mandatory requirement here being the ability to distinguish topographic map series and their resolutions 2. Database to store cartographic information a) Must be pre-populated from the library catalog b) Must allow additional information to be added for each map 3. Be easily extensible from both the administrator’s perspective and from future developers’ perspectives The system may have the following functional requirements: Undecided 1. An interface to updating the map database with a more current catalog version, while maintaining additional metadata may be necessary. 2. The scope of and the amount of metadata we display for each cataloged map. It is possible that for basic purposes we may only present a user with a link to the library catalog entry for a particular map. 3. The administrative interface may not need to be web-based.4. The functionalities to search, delete and modify metadata may need to be available. Optional 5. The zooming level may expand to the state/province level. 6. The boundaries of a region may be near-precise given the Group has access to a geo-decoding tool. Non-functional requirements are unspecified at this point. Foreseeable non-functional requirements may include: up-time, reliability, number of concurrent users supported, response time of the system, etc. Technical Requirements – Feasibility: 1. Server – The system is going to be running on a server in Olin Library. The Group is currently working on a contact to find out exactly who would be in charge of this server. If nothing else, the Group could definitely be given a test server in Mann to test the development code on. Most of the libraries servers are Linux servers. 2. Database – The current library catalog system is hosted on an Oracle database. The Group will have access to this database, and permission to add tables as needed for the inventory control system. 3. Web – The system will need to be integrated with the current library web page, which uses common web technologies. The library staff is flexible about loading on new technologies if needed. 4. Map – The interactive map can be done by using Google Maps API, Yahoo! Maps API, TerraServer, and others. After some research of the various technologies, the Group has decided that Google Maps API works best for the project. 5. Geo-decoder – The system needs a geo-decoder to map longitude-latitude pairs into region/country codes/names. Currently, the Group has not found a public tool or service that provides this functionality. Without this tool, the Group will have to reside on a rough workaround, by first finding out the maximum and minimum longitude and latitude pairs of the various regions, and define a rectangular region in which a user may click on to select the region that the rectangular region is approximating. Scope: For the purposes of this project we are solely concerned with exposing the Olin librarymap collection through an intuitive UI supported by an administrative interface. Development to the extent called out in the above requirements section is all that is planned. The end product will run on an Olin library web-server and will be viewable through all standard web-browsers. We DO NOT plan to make other library resources available through this interface. We DO NOT plan to expose the additional metadata to the library catalog nor any interface other than a map-based UI. We understand that it is NOT necessary to dynamically link with the library’s central database, so maintaining a separate database is a viable option. Suggested Deliverables: Management Deliverables: 1. Requirements Analysis – a document and a presentation to go over the formal requirements of the project, both functional and non-functional. This deliverable ensures that the Group is working on a system that closely matches to the wishes of the Client. This deliverable gives the Client a chance to modify and correct items that were mis-communicated or missed


View Full Document

CORNELL CS 501 - Feasibility2

Documents in this Course
Quiz 2

Quiz 2

2 pages

Usability

Usability

31 pages

Quiz 1

Quiz 1

2 pages

Stulba;''

Stulba;''

33 pages

Load more
Download Feasibility2
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Feasibility2 and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Feasibility2 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?