The IPA/IPL shall provide metadata management services.
3.2.4.1 Metadata Database Maintenance Services
The IPA/IPL shall provide Metadata Database Maintenance Services that provide functionality to populate, update, and link metadata items.
3.2.4.2 Metadata Population Services
3.2.4.2.1 The IPA/IPL shall have a Metadata Population Service.
3.2.4.2.2 The IPA/IPL Metadata Population Service shall provide the capability to accept, parse, and index metadata.
3.2.4.2.3 The IPA/IPL Metadata Population Service shall provide the capability to accept, parse, and index metadata as input in a metadata formatted file.
3.2.4.2.4 The IPA/IPL shall validate the metadata of incoming items.
3.2.4.2.5 Metadata will be validated for completeness to include the following mandatory fields: Classification, Producer Code, Product File Size, Product Short Name, and Time of Collection.
3.2.4.2.6 Metadata will be validated for correctness to include valid values and valid value ranges.
3.2.4.3 Metadata Update Service
The IPA/IPL Metadata Update Service shall provide the capability to update metadata index entries upon storage state changes such as purge and migrate upon accepting metadata entries.
3.2.4.4.1 The IPA/IPL Link Service shall provide the capability to create "complex" items, such as a target folder, by linking repository metadata index entries.
3.2.4.4.2 The IPA/IPL Link Service shall provide the capability for a user to specify data linkages.
3.2.4.4.3 The IPA/IPL Link Service shall provide the capability to maintain data links.
3.2.4.4.4 The IPA/IPL Link Service shall provide the capability for a user to navigate data links.
3.2.5 Resource Management Services
3.2.5.1.1 The IPA/IPL Resource Management Services shall provide the IPA/IPL Manager the capability to monitor data on available storage space, and to manage it on-line.
3.2.5.1.2 The IPA/IPL shall manage data across hierarchical storage devices as a single domain.
3.2.5.1.3 The storage management capability shall process transactions (i.e., reading and writing from disk) interactively, transactionally, or in batch mode.
The IPA/IPL Resource Management Services shall provide data management through the use of conditions (that, for example, would allow some users to query and save while allowing others to query only).
3.2.5.3 Migration Across Hierarchical Storage
3.2.5.3.1 The IPA/IPL Resource Management Services shall provide the capability to manage the migration of data across hierarchical storage devices.
3.2.5.3.2 The IPA/IPL Resource Management Services shall provide the capability to automatically migrate data across its hierarchical storage devices.
3.2.5.3.3 The IPA/IPL shall provide the capability to migrate data across hierarchical storage devices based on age of data, frequency of retrieval, and date of last retrieval.
3.2.5.3.4 The IPA/IPL shall provide the capability for an operator to manually migrate data across the hierarchical storage devices.
3.2.5.4 Library Service Statistics
The IPA/IPL Resource Management Services shall provide the capability to compile statistics on library services.
The IPA/IPL Resource Management Services shall provide for a unitary logon for shared data into the A3I libraries.
3.2.5.6 Metadata Database Backup
The IPA/IPL Resource Management Services shall provide for metadata database backup.
3.2.5.7 Metadata Database Recovery
The IPA/IPL Resource Management Services shall provide for metadata database recovery.
3.2.6 Data Management Services
The IPA/IPL shall provide Data Management Services to manage import, export, and purging of imagery and imagery products.
3.2.6.1.1 The IPA/IPL Import Service shall provide the capability to allow storage of imagery and image-based products in the libraries either manually or automatically.
3.2.6.1.2 The IPA/IPL Import Service shall provide an Application Program Interface (API) for both a graphical and a keyboard interface to support user specifications of data to be populated into a library.
3.2.6.1.3 The IPA/IPL Import Service shall support user identification of file format and compression of data to be imported from a client.
3.2.6.1.4 The IPA/IPL Import Service shall provide the capability to import and archive images and image products from both CD and magnetic media.
3.2.6.1.5 The IPA/IPL Import Service shall be capable of filtering products based on Area of Interest (AOI), Country Code, and Image Resolution.
3.2.6.1.6 The IPA/IPL import service shall be capable of selected metadata field population for imported image files based on the source (i.e., IP address) of the imported file.
3.2.6.1.7 The IPA/IPL Import Service will support the generation of a thumbnail for each archived image (or image product) imported in the following formats: NITF 2.0, TFRD, TIFF 6.0, GIF, Sun Raster, and Kodak 7700. The thumbnail will be linked to the associated image metadata for use by the IPA/IPL Query/Browse service.
3.2.6.1.8 The IPA/IPL will create an R5 image overview for each image input file meeting user defined metadata criteria. The IPA/IPL will link the overview to the associated full frame image file.
3.2.6.2.1 The IPA/IPL Export Service shall support requests to copy an entire image or image-based product as a file, an image subset as a file-based image extraction, or a group of pixels from a library into user-specified location. Image subsets can be extracted from only those imagery files that contain Support Data Extensions (SDE) metadata.
3.2.6.2.2 The IPA/IPL Export Service shall provide an API for both a graphical and a keyboard interface to support user specification of data to be retrieved from the NIL, CILs, and IPLs.
3.2.6.2.3 The IPA/IPL Export Service shall support user identification of file format, and compression of data to be exported from a library.
3.2.6.2.4 Unserviced IPA/IPL export requests shall be processed in priority order as soon as resources become available.
3.2.6.2.5 The IPA/IPL Export Service shall allow the exporting of imagery, or a portion of an image (image chip), based on a user defined "stretchy box" overlaid on a map or image.
3.2.6.2.6 The IPA/IPL shall allow the user to identify the Reduced Resolution Data Set (RRDS) (R0 through R7) of the image to be exported from the library.
3.2.6.3.1 The IPA/IPL Purge Service shall provide the capability to remove imagery and related metadata from library storage.
3.2.6.3.2 The IPA/IPL Purge Service capability shall be established based on metadata attributes, frequency of retrieval, linkage to other items, and date of last retrieval.
3.2.6.3.3 The IPA/IPL Purge Service shall provide the capability to sever the links between the purged item and any linked item.
3.2.6.3.4 The IPA/IPL Purge Service shall be capable of establishing purge criteria based on expiration date, exploitation complete, or time in system.
3.2.7.1 The IPA/IPL shall provide a Query Service which provides interface to support user queries, provides a locator capability, and aggregates query responses. The Query Service provides the capability for users to submit queries to a local library or to search multiple A3I libraries based on specific metadata attributes associated with the needed image products, using either positive or negative logic query quantifiers.
3.2.7.2 The IPA/IPL Query Service shall support user discovery of imagery and/or image-based products that meet specified query criteria or parameters by providing a list of image product file(s) that meet the parameters of the clients query and the library location of said file(s).
3.2.7.3 The IPA/IPL Query Service shall provide the capability for users to specify whether queries are submitted to all, some, or one IPA/IPL.
3.2.7.4 The IPA/IPL Query Service shall provide an API for both a graphical and a keyboard interface to support user queries.
3.2.7.5 The IPA/IPL Query Service graphical and keyboard interfaces shall support associative queries to define a set of imagery or image-based products based on a subset of image attributes as defined in the Standards Profile for Imagery Archives (e.g.) target identifier, target name, date, country code, mission number.
3.2.7.6 The IPA/IPL Query Service graphical and keyboard interfaces shall support navigational queries to define a set of imagery or imagery-based products based on relative temporal or geo-spatial image characteristics.
3.2.7.7 The IPA/IPL Query Service shall have the capability to aggregate the query responses and return the aggregate as a single response to the client.
3.2.7.8 The IPA/IPL Query Service shall provide the capability to display the first user specified number of listings which match the query criteria. Additional matches shall be displayed following user interactive request.
3.2.7.9 The IPA/IPL Query Service shall provide a user the capability to request the termination of an ongoing search before it completes.
3.2.7.10 Query termination shall be capable of being specified based on user-specified elapsed time, the number of item satisfying the query options, or the manual intervention of the user.
3.2.7.11 The IPA/IPL Query Service shall provide the capability to aggregate the completed query responses and return the aggregate as specified by the user when the search is prematurely terminated.
3.2.7.12 Unserviced query requests shall be processed in priority order as soon as resources become available.
3.2.7.13 The IPA/IPL Query Service shall be configurable such that queries return products, notifications, and full or partial metadata.
3.2.7.14.1 The IPA/IPL shall provide a Browse Service to support a user's interactive review of data such as that returned in a query response. This data includes thumbnail overviews of images, imagery products, or metadata associated with the imagery or imagery product.
3.2.7.14.2 The IPA/IPL Browse Service shall present thumbnail overviews (sub-sample imagery pixels, or textual) of images or image-based products in the query result.
3.2.7.14.3 The IPA/IPL Browse Service data view options shall include an individual browse image display.
3.2.7.14.4 The IPA/IPL Browse Service data view options shall include a text-based listing.
3.2.7.14.5 The IPA/IPL Browse Service data view options shall provide the capability to display metadata elements in addition to those specified in the query.
3.2.7.14.6 The IPA/IPL Browse Service data view options shall include a graphically-based display of images or image-based product footprints overlaid on, and registered to maps.
3.2.7.14.7 The IPA/IPL Browse service shall provide the user with the capability to define the options/defaults of the display response as follows:
3.2.7.15.1 The IPA/IPL shall provide a Notification Service. Notification is on a library basis, requiring user notification profiles to be registered on the libraries of interest.
3.2.7.15.2 The IPA/IPL Notification Service shall alert the user when new imagery or imagery products that satisfy a given profile's criteria are available for access from imagery libraries.
3.2.7.15.3 The IPA/IPL Notification Service shall provide the user the capability to specify the frequency of notification.
3.2.7.15.4 The IPA/IPL Notification Service shall provide the capability to specify that notification shall occur at client log-on or at a specific time of day.
3.2.7.15.5 Notification at sign-on shall include new imagery and imagery products since last logoff.
3.2.7.15.6 The new product notification capability shall be selectable in user profiles.
3.2.7.15.7 The period of notification for new product notification shall be site selectable and validated by the IPA Manager.
3.2.7.16.1 The IPA/IPL Retrieval Service shall provide the capability to enable the user to retrieve data from the library based on query responses, image or image product ID, data availability notification, and browse responses.
3.2.7.16.2 The IPA/IPL Retrieval Service shall allow the retrieval of imagery, or a portion of an image (image chip), based on a user defined "stretchy box" overlaid on a map or image.
3.2.7.16.3 The IPA/IPL Retrieval Service shall retrieve data from a library based upon user request options (i.e. desired format, compression rate, FTP destination address).
3.2.7.16.4 The IPA/IPL Retrieval Service shall allow a user to create pre-defined (i.e. canned) requests for data.
3.2.7.16.5 The IPA/IPL Retrieval Service shall allow the user to save pre-defined requests for data.
3.2.7.16.6 The IPA/IPL Retrieval Service shall provide the capability to terminate a retrieval request.
3.2.7.16.7 Unserviced IPA/IPL retrieval requests shall be processed in priority order as soon as resources become available.
3.2.7.16.6 Brokered Retrieval Service
3.2.7.16.6.1 The IPA/IPL Retrieval Service shall provide a brokering capability between a user and multiple libraries that contain requested imagery or imagery products such that the retrieval is directed to a library that provides potentially, the most timely response.
3.2.7.16.6.2 The IPA/IPL Retrieval Service shall accept a Library Retrieval Request that identifies the items and the libraries at which the requested items are stored.
3.2.7.16.6.3 The IPA/IPL Retrieval Service shall select the library from which the requested item is to be retrieved based on several conditions.
3.2.7.16.6.4 The IPA/IPL Retrieval Service shall select the library from which the requested item is to be retrieved based on communications capacity (rate).
3.2.7.16.6.5 The IPA/IPL Retrieval Service shall select the Library from which the requested item is to be retrieved based on dissemination dispatch queue size.
3.2.8.1 The IPA/IPL shall provide administrators with the ability to monitor and effect the use and behavior of its internal data, storage, and processing resources.
3.2.8.2 Each IPA/IPL shall provide a System Administrative Service to support initialization, operation, and shutdown.
3.2.8.3 Each IPA/IPL shall provide a Performance Management Service to measure, predict, and optimize its performance over time.
3.2.8.4 The IPA/IPL Server and Client will support remote diagnostics efforts. The IPA/IPL Server and Client shall support remote downloading of software updates from the APMO Customer Service Center (ACSC).
3.2.9.1 The IPA/IPL Profile Service shall provide the capability to automatically disseminate a given item to a user, or notify the user of the item's existence, based on a pre-defined set of user specified criteria.
3.2.9.2 The IPA/IPL Profile Service shall provide the capability to accept and maintain retrieval and notification profiles.
3.2.9.3 The IPA/IPL Profile Service shall provide a user the capability to define a notification profile request to establish the criteria for automatic dissemination or notification of new imagery or imagery products.
3.2.9.4 The capability to specify when notification occurs shall be selectable by the user in the notification profile.
3.2.9.5 The IPA/IPL Profile Service shall provide a user the capability to define a retrieval profile request that specifies particular imagery or imagery products that are to be automatically retrieved.
3.2.9.6 The IPA/IPL Profile Service shall accept contingency retrieval profiles (i.e., linked to events and war plans).
3.2.9.7 The IPA/IPL Profile Service shall support the identification of multiple recipients for each retrieval profile.
3.2.9.8 The IPA/IPL Profile Service shall support at each library the registration of 5000 unique retrieval profiles.
3.2.9.9 The IPA/IPL Profile Service shall accept a Library Retrieval Request from a retrieval profile that identifies the items and the libraries at which the requested items are stored.
3.2.9.10 The IPA/IPL Profile Service shall support user identification of imagery, image-based products, or image subsets consisting of image tiles, chips, or pixels.
3.2.9.11 The IPA/IPL Profile Service shall support user identification of file format, compression, and destination address.
3.2.9.12 The IPA/IPL Profile function shall include a template capability to allow users to save and store "canned profiles".
3.2.9.13 The IPA/IPL shall accept externally generated profiles.
3.2.9.14 The IPA/IPL shall be capable of processing profiles based on area of interest, image time stamp, data type, source, and quality.
3.2.9.15 The IPA/IPL Profile capability shall be capable of returning products, notifications, and full or partial metadata.
3.2.9.16 The IPA/IPL Profile shall allow specifying the dissemination priority.
3.2.9.17 The IPA/IPL Profile shall aggregate by recipient, products that meet profile criteria.
The IPA/IPL shall provide the capability to support the century roll-over in all functionality.
3.2.11 Remote Software Maintenance
The IPA/IPL shall provide the capability to provide remote software maintenance that will support the ability for remote diagnostics and electronic update of software patches on IPA/IPL workstations, if site approved.
3.2.12 Automated Installation Process
3.2.12.1 The IPA/IPL shall provide an automated installation process for both the Server and the Client enabling users (which includes everyone who uses an IPA client) to install and configure clients at their sites.
3.2.12.2 The IPA/IPL shall provide documentation, both hard copy and on-line, for the automated install process.
The IPA/IPL shall provide on-line documentation that is stored in a format that is optimized for the IPA/IPL Servers. On-line documentation shall consist of the following:
The IPA/IPL boolean logic shall include negative logic to support all queryable IPA elements.
3.2.15 Hypertext Markup Language (HTML) Interface
3.2.15.1 The IPA/IPL HTML interface shall allow web browsers the same access to IPA/IPL services and functionality as the IPA/IPL Client application.
3.2.15.2 The IPA/IPL HTML interface shall provide the ability to query indices (i.e., metadata) of commercial, civil, and foreign satellite imagery stored at DIA.
3.2.15.3 The IPA/IPL HTML interface shall provide the capability to place on-line orders for raw commercial, civil, and foreign satellite imagery.
3.2.15.4 The IPA/IPL HTML interface shall provide the capability to view multiple thumbnails (thumbnail gallery) in support of multi-layered products.
The IPA/IPL shall process NITFS 2.0 tagged extensions in accordance with the NITFS PIAE, version 2.0. This standard supersedes all requirements as stated in RFC 00A-304J.
The IPA 1.2.2 shall provide the system operator with on-line display of:
All versions of IPA/IPL, beginning with IPA 1.2.2, shall be backward compatible with the previous version.
3.2.19.1 The IPA/IPL queriable indices shall comply with the SPIA as modified to accommodate commercial, civil, and foreign satellite metadata elements.
3.2.19.2 The IPA/IPL will support the ordering of commercial, civil, and foreign satellite imagery stored at DIA.
3.2.19.3 The IPA/IPL shall provide access to indices (i.e., metadata) of commercial, civil, and foreign satellite imagery stored at DIA.
The IPA/IPL shall have the capability of automatically logging off inactive users after a programmable time-out period.