Data Manager’s Conference Data Store and NatureBib

1. Data Manager’s ConferenceData Store and NatureBib April 3, 2008 Brent Frakes

2. Overview • Current Systems • Data Store & NatureBib are silos with some functional overlap • Consists of core components which can be shared with other NPSpecies and other applications • Deconstruction & Reconstruction • Data Store & NatureBib are being deconstructed into core services • These services are then reconstructed to provide improved Data Store and NatureBib functionality • Services are also available for integration with other applications • User driven design • IRMA team is starting the process of deconstructing and reconstructing Data Store and NatureBib • Development will start in early 2009 • Involving end-users throughout design and development process

3. Discussion Topics • Current System • Deconstruction & Reconstruction • User Driven Design Process • Conclusion

4. Current System • NatureBib • Database for scientific citations • Synchronized with NPSpecies • Data Store • Metadata and data file mgmt • Based on existing FGDC standards • Supports Geospatial One Stop, others

5. Current System - Issues

6. Current System – Issues (continued) • Users do not know where to upload files • Inconsistency – sometime files in Data Store, sometimes in NatureBib • Redundancy – sometimes files in both places • Files not put in context • Need to associate with projects • Need to associate with protocols • Need to associate with workflows • Voucher and Observation data hidden in Access databases and other files • Versioning • Same file sometimes generated on recurring basis • No way of associating these files

7. Discussion Topics • Current Status • Deconstruction & Reconstruction • User Driven Design Process • Conclusion

8. Deconstruction & Reconstruction • Deconstruct applications into discrete functions • What are the distinct functions performed by these applications? • How may these functions be improved? • What functions are missing? • Reconstruct discrete functions into services • Can these functions be shared by multiple applications? • What are the essential tasks performed by each function? • What services can be built from these discrete functions?

9. Data Store – Serves Two Audiences • Data Store serves two distinct audiences: • Natural Resource Audience • Bundle files related to a given project • Find documents by variety of criteria: Unit, Air, Fire, Land Use, etc. • Support scientific research • GIS Audience • Generate spatial relationships among various data sets • Visualize natural resource information • Store, transform, and distribute metadata • Conclusion • Perhaps we should decouple Data Store into two distinct services? • Natural Resource Services – Support Natural Resource workflows • GIS Services – Support GIS workflows • Current focus – Natural Resource Services

10. Discrete Functions – Data Store • Projects • Bundle files related to a given project • Identify projects by related Taxonomy, Units, etc • Protocols • Manage protocols for each type of project • Define data collection templates for each protocol • Define ways to automate extraction of voucher & observation data from templates • Reports • Store final reports

11. Discrete Functions - NatureBib • Serve as a card catalog for Natural Resource literature • Reference data internal to NRPC systems • Reference data in various Parks, other computing systems • Reference data stored in physical locations in non-digital format • Metadata Support • Generate Dublin-Core metadata • Generate FGDC metadata • Third Party application support • Support for ProCite desktop applications • Other third party end-user tools?

12. Data Store and NatureBib Services IRMA Pre- IRMA

13. Bibliography Service • Natural Resource Card Catalog • Central location for managing NR grey literature • Each entry may reference zero or more locations • Locations, or holdings, may be physical or digital • Does not manage any files • All files stored in File Services • These files also may be referenced by other services • Project Service -protocols and final reports • GIS Services – various products

14. Project Service • Projects • Single location for managing projects, whether planned, approved, or completed • ‘Show me all projects on the Pine Beetle in Rocky Mountain Region’ • Maintains references to all files created by each project… ‘bundling’ • Protocols • Manages protocols used for various Natural Resource projects • Manages data templates supporting these protocols (e.g. Access files, spreadsheets, etc.) • Permits • Assumes RPRS functions • Associated Files • Project files uploaded through this service… • … then sent to File Services for storage • Bundles all files related to project • Reports are automatically registered with Bibliography Service

15. Data Extraction Service • Automates extraction of data from Access, Excel, and other data templates • NPSpecies • extracts data from desktop application • Protocols • extracts observations and vouchers from protocol templates, puts into other services • Others? – to be defined

16. File and Multimedia Services • File Services • Single location for storing files • Project Service • Reports, raw data files, access databases, etc. • Bibliography Service • Digital copies of Natural Resource grey literature • Other Services • Templates, protocols, etc. • Multimedia Services • Transform images • Manage audio clips • etc.

17. Discussion Topics • Current System • Deconstruction & Reconstruction • User Driven Design Process • Conclusion

18. User-Driven Development Organization Three distinct opportunities for end-user involvement: • Between Versions • User Needs Conference Calls • Workshops • Before Development • Review Requirements • During Development • Review deliverables • Request Changes to Requirements

19. Request Enhancements • User Needs Conference Calls • NRPC needs to know how you want to use a service • We will request you attend one or more conference calls to discuss your needs • Workshops • Invite key staff to participate in workshops • Prioritize user needs identified in conference calls

20. Review Requirements • Formalized Use Cases • What are the common scenarios for using a service? • What is the workflow for these scenarios • How do various staff use these scenarios • Portal Specifications • Use Visio to mock-up the portal user interface • Demonstrates functionality and workflow • Functional Requirements • The nitty-gritty details of how a service is to work • Developers use this document to implement the service • QA staff use this document to test this service • Change Control Board use this document to approve enhancements

21. Iterative Development • IRMA performs iterative development • Biggest risks are tackled first • Each iteration results in an executable deliverable • Not all executable deliverables, however, involve portal enhancements • Users invited to review each iterative deliverable • Deployed on a test server • Each iteration will result in a SameTime session to review new functionality • User feedback is solicited, incorporated into next iteration as possible

22. Discussion Topics • Current System • Deconstruction & Reconstruction • User Driven Design Process • Conclusion

23. Conclusion • Data Store and NatureBib are application silos • Introduce confusion, redundancy • Do not necessarily serve user needs • Deconstruction & Reconstruction • Currently deconstructing these applications into services • These services will be reconstructed to meet your needs • These services will also meet other functional needs • User-Driven Design Process • NRPC has User-Driven Development Organization • User requirements sessions to start in next couple months