Roadmap

From FilteredPush
Jump to: navigation, search


Project Charter Project Roadmap Requirements ApplePie

Public Roadmap

To be filled in here then moved to another page when we are happy with them.

SPNHC DEMO WEEK OF 2012-JUN-10

"Target for SPNHC: (i) collecting annotations from a client; (ii) transporting annotations through an FP network that identifies recipients; (iii) the recipients ingest the annotations into their databases 2nd wk of June 2012 Consenus on this target." (2011Oct25)

  • Demonstration at SPNHC 2012 (June 2012).
    • Target Use Case: Annotate Specimen
    • Make new determination annotation in Morphbank(and/or Symbiota).
    • Transport annotation through a FilteredPush network instance consisting of at least three network nodes.
    • View annotation in Mapper UI at instance of Specify6 database.
    • Accept and ingest annotation into Specify 6 database, with resulting action annotation sent to network.
    • View, in web client to network, base harvested record plus new determination annotation plus action annotation recording acceptance of new determination.
  • Early Fall 2012
    • Target Use Case: Remote Data Capture
    • Transcribe new specimen record from label images in Morphbank.
    • Transport new specimen record annotation FilteredPush network instance.
    • View annotation in Mapper UI at instance of Specify6 database.
    • Accept and ingest new specimen record annotation into Specify 6 database, with resulting action annotation sent to network.
    • Implement automated ingest of authorized new specimen record annotations.
    • Define a quality control test for harvested data, implement as a kepler workflow embedded in a network analytical capability.
    • Enable end user authentication through DataOne services.
    • Network architecture uses configurable pipes rather than static node configuration.
  • End of 2012
    • Target Use Case: Find Duplicates
    • Implement find duplicates use case within Specify6.
    • Target Use Case: Quality Control New Record
    • Implement potential duplicate detection as Kepler workflow embedded in network.
    • Deployed Network to support SCAN TCN
    • Deployed Network to support NE Vascular Plants TCN

Related

TASK LIST IN MANTIS ("Issue tracking: SourceForge MantisBT." 2011Nov08)

Diagram of Network, Components, Capabilities, Clients, and Broad Buildout Plan
Components of ApplePie instance of FilteredPush Network


Key Milestones

Organized by targets they support.

Demonstration at SPNHC 2012 (June 2012)

Target Use Case: Annotate_Specimen

  1. Target
    1. FP Access point able to accept encrypted, signed FP Messages, return a message ID, pass the message to Triage, job planner able to create job plan, triage able to pass job plan to job runner.
    2. Job runner able to locate network capabilities for executing steps in job plan from static network configuration.
    3. Annotation store able to accept annotations from a a job runner.
    4. Message distribution system able to deliver an annotation message to an interest based on values found in the message.
    5. Message distribution system able to deliver an annotation message to an interest based on values not present in the message.
    6. FP network able to accept subscribe to query messages, create corresponding interests, and allow clients to poll those interests.
    7. Annotation Processor able to retrieve an annotation message from an interest, display it to a user, and ingest the content of the annotation into a Specify6 instance. Requirement3
    8. Annotation Processor able to retrieve an annotation message from an interest, display it to a user, and ingest the content of the annotation into a Specify6 instance, and generate corresponding response annotation.
  2. All shown except for the following, not complete.
    1. FP Access point able to accept encrypted, signed FP Messages.
    2. Job runner able to locate network capabilities.
    3. Message distribution system able to deliver an annotation message to an interest based on values not present in the message.

Project complete 2015-June-30

Key milestones

  • Transcription of label data into new specimen records within Symbiota, transport of new specimen record annotations for ingest into Specify6.
  • Capture of selected annotations (new determinations) within Morphbank, transport of annotations for ingest into Specify6.
  • Kepler engine able to function as FP Network analytical capability.
  • Dynamically configurable network nodes
  • Deployed Network to support SCAN TCN
  • Deployed Network to support NE Vascular Plants TCN

Current Status

Note: Edit the current status to reflect the current status of each component.

Open Issues

Closed Issues

The code behind the demonstration is the actual implementation. Using MongoDB as "global knowledge", using polling on subscription queries rather than pub-sub, and a client that manages subscriptions for users registered with the client.

  • Dev Environment: All projects now using Maven for dependency management. Junit tests for core functionality contained within FP-Core. Embedded datastore implementations: TDB (triplestore) and OrientDB (documentstore) can be used during development along with MongoDB (not embedded, install required). Integration testing and development can be done using embedded Jetty configured for JavaEE support using OpenEJB however the embedded config is not likely to be scalable enough for production use.
  • Documentation: Deployment projects contain minimal readme with deployment instructions. All classes in FP-Core have been documented via JavaDocs. Classes in FP-Service still need comments and JavaDocs. Architectural diagrams need to be updated to reflect recent refactoring to support asynchronous messaging (via Apache Camel Routes and JMS).
    • Dev Environment and Build docs: see http://filteredpush.sourceforge.net/pages/devenvironment.html for setting up the dev environment (needs to be updated for Java 7 but otherwise still relevant), http://filteredpush.sourceforge.net/pages/devprojects.html for building projects using maven (needs updating, process is still much the same however the project structure has changed), and http://filteredpush.sourceforge.net/pages/eclipsedebugger.html for deployment and debugging using Eclipse (does not cover embedded configuration, only applies to Glassfish deployment).
    • UML Model for Network Extensive design work, including classes and sequence diagrams. Generated code. Codebase has diverged from this generated code and model. Many of the concepts in original UML model map to functionality provided by Camel (see http://camel.apache.org/enterprise-integration-patterns.html)
    • FP Client API Definition Working on consolidating FP-PHP-Library and FP-ClientHelper to provide client helper services to clients via REST or Java classes. Refactored client helper uses an implementation of a Camel RouteBuilder to provide underlying services to clients.
    • Development documentation for Network Components FP-Core has JavaDocs checked in with classes, need to upload to SourceForge. FP-Service APIs needs JavaDocs (Services, AccessPoint, ClientHelper, etc). Need updated documentation for different deployment scenarios (embedded, glassfish, etc).
      • Annotation: AO/AOD Manuscript on AOD under revision per reviewer comments. AOD and examples tightened up and available for download on SourceForge: http://sourceforge.net/projects/filteredpush/files/SemAnnMutableDataV0994/ AO/AOD examples refactored into OA. Abstract for annotation generator (rdfhandler) submitted to TDWG.
      • FP Messages: From prototype. Need revision. See: FP Messages Message definitions in UML, need to go to wiki. FPMessage and content types now defined in xsd. Added complex types for content types (i.e. AnnotationContent, QueryContent, AnalysisParams, etc).
    • Code: http://sourceforge.net/p/filteredpush/svn/HEAD/tree/branches/FP-Deployments/
      • FP-Core: Contains knowledge APIs and datastore implementations for: MongoDB, OrientDB (embedded), Fedora, Fuseki, TDB (embedded), and Mulgara. Contains FP-Message classes and Model for annotation generation and serialization/deserialization of SimpleDarwinCore/DwcFP. Also contains, configuration management, xml dsig authorization/signing code, and several utility classes for dealing with documents, rdf, and sparql.
      • FP-Service: Contains message driven service classes (Jobs), accesspoint, camel routebuilder implementation (triage/job planner/job runner). Client helper services are currently located in this project but should be factored out eventually. This includes a ClientHelper implementation, ClientConnector RESTful webservice, AnnotationBuilder and validation services, MessageFactory for building FP-Messages.
    • Deployment instructions Most recent instructions contained within the following readme: http://sourceforge.net/p/filteredpush/svn/HEAD/tree/branches/FP-Deployments/README.txt. The rest of the documentation will need to be updated. Old deployment instructions up for building and running current implementation. Information about prerequisites and deployment process should still apply (needs review however). See:Build_and_run_FP_in_Eclipse, SPNHC_2012 Demo Deployment, FP-Lite_deployment for SCAN. Updated deployment instructions for FP Medium: http://filteredpush.sourceforge.net/pages/medprereq.html and FP-Lite: http://filteredpush.sourceforge.net/pages/liteprereq.html used for the deployment of SPNHC demo branch.
  • Clients
    • Annotation Processor: Needs to be updated to use new ClientHelper and Annotation generation code (RDFBeans). Needs refactoring/bug fixes to get to a stable state. Currently working on providing some functionality as jQuery plugins in Symbiota, Morphbank etc as an alternative for SCAN.
      • can parse/validate the annotations through the predefined Sparql queries.
      • can communicate with the messaging system of the FPush network to get interested annotation, send out response annotation, search for the annotations (after integrating with the new messaging system API)
      • can communicate with the specify driver based on the data policy to get, add and update the specify database with the proposed change.
      • Web interface is developed to allow the collection manager to register interest on the annotations; browse, search, delete the incoming annotations; check the detail of the annotation (including its response, and the error/warning during the annotation parsing); respond the annotation; apply the proposed change to the local data source.
      • Has the ability to launch an analysis on harvested occurrence record data using an available workflow. A query (on taxon, collectionCode, etc) can be specified to narrow the set of records that the analysis should apply to.
      • Two level/sheet spreadsheet view and export of analysis results as csv or xsl.
      • Drivers:
        • Driver API documentation:
        • Specify6 Driver. OAuth removed, Annotation Processor now tied to a single datasource and pre-configured credentials.
        • Specify-HUH Driver.
        • MCZbase Driver.
    • Annotation Generation: Can generate annotation RDF for new/updated annotations from a Specify Database. Can generate the following apple pie annotations (update georeference, new determination, update determination, response annotation, solve with more data, new occurrence). Using RDFBeans + Jena for serialization and deserialization of annotation data (xml or json) to and from multiple rdf formats (rdf/xml, n3, etc): http://rdfbeans.sourceforge.net/. Uses classes that contain metadata about mappings as Java annotations.
    • MorphBank: Needs updating to use latest version of ClientHelper
    • Symbiota: Can build, install and run Symbiota See: Installing_Symbiota. Needs updating to use latest version of ClientHelper.
    • Web Client: Integrated Annotation processor and reworked prototype web client implementation as UI for Annotation Processor.
    • Specify: Can build, install, and run Specify with test data. See: Installing_Specify
    • Kepler Client: Kepler Kuration package.
  • Network
    • Access Point/Triage/Job Planner/Job Runner: Code generated from design documents and modified. Working single node Tomcat servlet implementation of a FP Access Point web service over Triage/JobPlanner/JobRunner in code tagged for SPNCH Demo. Working single node Glassfish container implementation of a FP Access Point web service over EJB Triage/JobPlanner/JobRunner in code tagged for SPNCH Demo. Refactoring EJBs to MessageDriven Beans to allow asynchronous communication between clients and the AccessPoint. Improved configuration (replacing properties files with injected Resourced) and decouped clients from network node code via use of Apache Camel and enterprise integration patterns.
    • Lightweight Annotation System SparqlPUSH no longer being used, FP-Lite functionality that overlaps with FP-Medium has now been consolidated to make code more maintainable. Lightweight system is using a subset of all available services (specifically the AnnotationService).
    • Implemented jobs for message types:
      • FPMessageType=PING, Job=PingJob (Needs change to NETWORK_STATUS), ping should just produce a PONG from the access point, not a job.
      • FPMessageType=QUERY, Job=ApplePieSparqlQueryJob
      • FPMessageType=ANNOTATION, Job=ApplePieAnnotationJob
      • FPMessageType=FP_FIND_SETS, No implementation yet. Job=ErrorJob
      • ApplePieMessageType=NOTIFICATION, No implementation yet. Job=ErrorJob
      • ApplePieMessageType=REGISTER_INTEREST, Job=ApplePieRegisterInterestJob
      • ApplePieMessageType=DELETE_INTEREST, No implementation yet. Job=ErrorJob
      • ApplePieMessageType=FIND_DUPLICATES, No implementation yet. Job=ErrorJob
      • ApplePieMessageType=RUN_ANALYSIS, Implementation invokes an instance of kepler analysis Job=ApplePieRunAnalysisJob
      • ApplePieMessageType=ADD_ANALYSIS, No implementation yet. Job=ErrorJob
    • Network Transport Layer = Overlay Network: Nothing yet.
    • Network Capabilities
      • Data Store: Using Fedora as the default document store and Mulgara as the default triplestore for production deployments. Documents in Fedora can contain rdf metadata linking them to resources in Mulgara (the default triplestore used by Fedora for its "Resource Index". MongoDB used as a message store by Camel for support of asynchronous messaging (see http://camel.apache.org/guaranteed-delivery.html).
      • Knowledge: Workflows stored in Fedora. Interests can be registered on data in either Fedora (interested in workflows) or Fuseki (interested in Annotations). Interests framed as Sparql queries on Fedora's resource index return the fedora document ids and the items of interest are retrieved from Fedora using this query result. Mongodb messaging and knowledge implementation for kepler (storing the harvested occurrence records and the analysis results) and for storing and associating FPMessages with the results. Persisting interest queries as kvp in Fedora as an alternative to SparqlPuSH.
      • Client Authentication Implemented client authentication using xml digital signing of messages. Java code for the signing and validation for client use is in FP-Core. All clients use the xmldsig method of authentication when communicating with the accesspoint (via ClientHelper). Utility classes provided with client helper to allows clients to sign and construct messages.
      • Messaging Camel allows for the use of multiple messaging protocols. We are using JMS and message driven beans to support asynchronous messaging. FP-Message content is set as the message body (ObjectMessage) and the rest of the attributes are provided as properties. Messaging/Accesspoint uses "pipes" and "filters" for processing the message (checking auth, extracting message content and metadata and routing to appropriate destination, see http://camel.apache.org/pipes-and-filters.html)
      • Harvesting and network data cache
        • Data Providers: Some work on Specify6 OAI-PMH service.
        • Harvester: Harvester working, standalone, needs integration into the larger picture.
        • Network Cache & Index: Need to re-examine our needs regarding this.
      • PubSub: Not doing pub/sub anymore. Just polling on subscribed queries.
      • Analysis: Currently implemented an MDB (AnalysisService) that invokes the Kepler workflow engine. This still needs more work and testing with the new refactored AccessPoint. User can send workflow URL and workflow parameters through FP message to invoke an analysis work. Working on dependency management issues and creating a separate EAR for Kepler deployments. Still need to add Akka integration via Camel (no need to implement a Service in this case as Camel provides an Akka module: http://doc.akka.io/docs/akka/snapshot/scala/camel.html)
      • Generic Mapper: Currently reworking the SpecifyDriver.

Target Dates

2013-July-31

Live integration with SCAN Symbiota instance.

  • Delivery of annotations to interests based on related data not found in annotation Requirement20

2013-Aug-15

Live integration with NEVP Symbiota instance.

  • Network configured to encrypt all data in motion Requirement14
  • Deployment of Annotation Processor at HUH and one other NEVP Specify site (?UMass).

2013-Aug-31

  • Deployment of Annotation Processor with MCZbase/Arctos driver at MCZ.

2013-Sept-30

  • Deployment of Annotation Processor at all NEVP Specify sites doing primary digitization in 2013.

2013-Oct-28

TDWG - Demonstrate Find Duplicates.

Historical Target Dates


2012-Jun-10

Demonstration at SPNHC. Screencast: FP SPNHC 2012 demo.

Components for SPNHC 2012 Demo, key components in blue or green.


  • Documentation: Developer-level user-friendly documentation for downloading, building, installing, and running the demonstration SPNHC_2012 Demo Deployment.

The demonstration can be run temporarily on a minimum of three network nodes plus at least four clients as:

  1. a standalone MorphBank instance that can act as an annotation publication client Requirement22 Requirement23
  2. a standalone Symbiota instance that can act as an annotation publication client Requirement22 Requirement23
  3. a standalone web client instance that can issue queries, manage subscriptions Requirement19, and read notifications
  4. a network node providing a network access point, triage, job planning and job running
  5. an statically configured overlay network that allows network nodes to discover and access network capabilities
  6. network configured to encrypt all data in motion Requirement14
  7. a network capability providing a cache of data from multiple data providers with indexes
  8. a network capability providing a filtering pub-sub service Requirement20
  9. a network capability providing an annotation store
  10. implementation of job plans that allow
    1. publication of an annotation
    2. injection of query of the data cache and the annotation store (one time query)
    3. creation of an interest (subscription) expressed as a query (subscribe to a query) Requirement19
    4. delivery of annotations to interests based on both annotation content and related data Requirement20
    5. retrieval of accumulated messages on a subscription
  11. an annotation processing component that can be invoked to
    1. convert objects retrieved from a local data source to a standard network representation
    2. convert objects from a standard network representation to a representation ingestible local data source Requirement3
  12. an annotation processing user interface embedded in or configured to run alongside Specify6
    1. authorize and initiate the ingest of an object into a local data source Requirement3 Requirement4
    2. inform the network of actions taken in annotation processing Requirement5Soln
  • Critical path items planned for demonstration but not yet developed:
  1. Multiple node network.
  2. Network configured to encrypt all data in motion Requirement14
  3. A network capability providing a cache of data from multiple data providers with indexes
  4. Delivery of annotations to interests based on related data not found in annotation Requirement20

Subsequent Targets

 

Critical Path Things to Do

  • Find Duplicates Use Case (Supporting NE Vascular Plants TCN)
  • Remote Data Capture Use Case (Supporting NE Vascular Plants TCN)
  • Core Infrastructure
    • Delivery of annotations to interests based on related data not found in annotation Requirement20
    • SPARQL Push messaging system
    • Multiple node network with no single point of failure
    • Lightweight annotation system (Supporting iDigBio, Morphbank, Symbiota)
    • Network configured to encrypt all data in motion Requirement14
    • A second case of a Driver (Specify-HUH as simple case, Specify-NG as more complex).
  • Quality Control Data Use Case

Deployment Targets

  • Deploy into iDigBio infrastructure
  • Deploy ApplePie network (Supporting NE Vascular Plants TCN)
  • Deploy SCAN network (Supporting SCAN TCN)
  • Integrate with Production/Trunk Specify and Symbiota

Target List

2012-Jul-03

Code freeze for Botany 2012 Demo. Documentation of current system to plan refactoring.

  • Dev Environment:
    • Working deployment for Botany Demo on fpnode1-6.mcz
    • Specify set up on Botany Demo laptop, able to ssh tunnel to firuta. Issue 93
  • Documentation
    • UML Models: Class, Component, and Sequence diagrams of all current components produced to provide developer overviews (overviews, not comprehensive class diagrams). Issue 90 Issue 91 Issue 92 FP_Development_Documentation
    • FP Client API Definition Documentation of Client API.
    • Javadocs: Generated for each package with Hudson job to deploy to sourceforge website. Issue 76
      • Annotation:
      • FP Messages:
    • Code
    • Deployment instructions
  • Clients
  • Network
    • Access Point/Triage/Job Planner/Job Runner:
    • Network Transport Layer = Overlay Network:
    • Network Capabilities
      • Annotation Store:
      • Harvesting and network data cache
        • Data Providers:
        • Harvester:
        • Network Cache & Index:
      • PubSub: Report ready on SPARQL Push / Pubsubhubub messaging.
      • Analysis:
      • Generic Mapper:

Botany 2012 iDigBio Workshop

Dates: July 7-11, Talk on 11th. Workshop on 12th.

Code Freeze Date: July 3.

Target: Repeat of SPNHC demonstration with bugs and feedback ironed out.

2012-Jul-31

Able to demonstrate transcription of new specimen records from labels within Symbiota, transport of these to Specify6, and ingestion of these new specimen records into Specify.

Able to demonstrate creation of new georeferences, transport of these as annotations, and ingestion into at least two driver instances.

Refactoring Targets

  • Ontological Representation of DarwinCore
  • AnnotationProcessor/ClientLibrary/Driver
  • Facades for Jobs,JobRunner,NetworkCapabilities allowing development/testing outside Glassfish.
  • Dev Environment:
  • Documentation
  • Clients
    • Annotation Processor:
      • Drivers: Driver for Specify-HUH, Driver for Specify-NG
    • Client Helper:
    • MorphBank: Refine UI for new specimen data transcription with input from domain experts.
    • Symbiota:
    • Web Client:
    • Specify:
    • Kepler Client:
  • Network
    • Access Point/Triage/Job Planner/Job Runner: Extend job plans to executing analysies.
    • Network Transport Layer = Overlay Network:
    • Network Capabilities
      • Annotation Store:
      • Harvesting and network data cache
        • Data Providers:
        • Harvester:
        • Network Cache & Index:
      • PubSub:
      • Analysis: Kepler engine as network capability.
      • Generic Mapper:

2012-Aug-28

  • Document FP-Lite FP-Lite_deployment_for_SCAN and FP-Medium for SCAN and iDigBio.
  • Refactor Annotation Generation using Bridge pattern.
  • Deploy SCAN testbed instance for testing Symbiota integration. symbiota2.acis.ufl.edu

2012-Sept-30

  • Sourceforge Hosting: Migrate MantisBT and MediaWiki HostedApp installs to Sourceforge projectweb installations https://sourceforge.net/p/forge/community-docs/Hosted%20Apps%20Retirement/ Sourceforge currently has an end of life for hosted apps of 4th quarter 2012, with migration tools becoming available in Sept 2012 (and not yet available as of Sept 19th). SourceForge has also introduced an upgrade path to its new Allura platform, interrelationships between the two are not yet clear, and upgrading has potential issues that people have observed and potentially undesirable side consequences.
  • Annotation Processor documentation.

Early Fall 2012

  • New Email client metaphor UI for Annotation Processor.
  • Annotation generation and rules for add and update Date Collected (including imprecise dates and date ranges).
  • Component to generate email notifications of annotations of interest (request from SCAN users).
  • Target Use Case Remote Data Capture
  • Transcribe new specimen record from label images in Morphbank.
  • Transport new specimen record annotation through FilteredPush network instance to relevant target collection database Requirement20.
  • View annotation in Mapper UI at instance of Specify6 database.
  • Accept and ingest new specimen record annotation into Specify 6 database, with resulting action annotation sent to network.
  • Implement automated ingest of authorized new specimen record annotations. Requirement31 Requirement32
  • Define a quality control test for harvested data, implement as a kepler workflow embedded in a network analytical capability.
  • Enable end user authentication through DataOne services. Requirement32 Requirement24
  • Network architecture uses configurable pipes rather than static node configuration.
  • Refactor Tim's mapper code to produce a SQL level driver for MCZbase/Arctos
  • Deploy Network to Support SCAN TCN

2012 Oct 19

  • Dev Environment:
  • Documentation
    • User documentation End user documentation for Testing FP-Medium in SCAN.
    • UML Model for Network
    • FP Client API Definition
      • Annotation: Examples Refactored into OA.
      • FP Messages:
        • Query: Sparql Query to collect annotation statistics for SCAN.
        • Annotation: Support for New determination, update determination, new georeference, update georeference, new and update locality/collecting event (support new/update date collected).
    • Code
    • Deployment instructions FP-Medium deployment documentation for SCAN.
  • Clients
    • Annotation Processor:
      • Drivers: Specify6, Specify6-HUH, Specify-NG, Test version of MCZbase/Arctos.
    • Client Helper:
    • MorphBank:
    • Symbiota:
      • FP functionality Integrated into Symbiota trunk, enabled by configuration.
      • Page to display query on annotation statistics gathered from network.
    • Web Client:
    • Specify:
    • Kepler Client:
  • Network
    • Access Point/Triage/Job Planner/Job Runner:
    • Network Transport Layer = Overlay Network:
    • Network Capabilities
      • Annotation Store:
      • Harvesting and network data cache
        • Data Providers:
        • Harvester:
        • Network Cache & Index:
      • PubSub:
      • Analysis:
      • Generic Mapper:
  • Deployments
    • SCAN TCN Symbiota FP-Medium in test use.

TDWG 2012

  • Oct 22-26.
    • David to present on FP-Lite, Maureen to present on Driver, James to run AGI, discuss OA.

2012 Nov 30

  • Dev Environment:
  • Documentation
    • User Documentation
    • UML Model for Network
    • FP Client API Definition Driver Documentation produced.
      • Annotation: Annotation examples, reworked to OA.
      • FP Messages: New execute workflow message.
    • Code
    • Deployment instructions Deployment documentation for FP-Medium. Updated deployment documentation for FP-Lite and for generating OA annotations (for iDigBio portal development).
  • Clients
    • Annotation Processor:
      • Drivers: Functioning drivers for Specify6, Specify-NG, Specify6-HUH, MCZbase.
    • Client Helper:
    • MorphBank:
    • Symbiota:
    • Web Client:
    • Specify:
    • Kepler Client:
  • Network
    • Access Point/Triage/Job Planner/Job Runner:
    • Network Transport Layer = Overlay Network:
    • Network Capabilities
      • Annotation Store: Document store and triple store working in FP-Medium
      • Harvesting and network data cache
        • Data Providers: OAI-PMH provider for Specify6 and Symbiota
        • Harvester: OAI-PMH harvester able to populate and maintain cache of data.
        • Network Cache & Index: Cache of harvested data.
      • PubSub: Able to notify interested parties for match on Institution/Collection and ScientificName in annotations.
      • Analysis: Embedded Kepler working in FP-Medium with a simple QC process.
      • Generic Mapper:
  • Deployments
    • SCAN FP-Medium in production use by SCAN.
    • ApplePie Test version of ApplePie FP-Medium running on iDigBio infrastructure.

2012-Dec-21

Blank Component List

  • Dev Environment:
  • Documentation
    • User Documentation
    • UML Model for Network
    • FP Client API Definition
      • Annotation:
      • FP Messages:
    • Code
    • Deployment instructions
  • Clients
    • Annotation Processor:
      • Drivers:
    • Client Helper:
    • MorphBank:
    • Symbiota:
    • Web Client:
    • Specify:
    • Kepler Client:
  • Network
    • Access Point/Triage/Job Planner/Job Runner:
    • Network Transport Layer = Overlay Network:
    • Network Capabilities
      • Annotation Store:
      • Harvesting and network data cache
        • Data Providers:
        • Harvester:
        • Network Cache & Index:
      • PubSub:
      • Analysis:
      • Generic Mapper:
  • Deployments