2012Nov21

From Filtered Push Wiki
Jump to: navigation, search


Etherpad for meeting notes: http://firuta.huh.harvard.edu:9000/FP-2012Nov21

Agenda

  • Annotations
    • Progress on: Rewriting examples/rules from AO/AOD to OA
  • ApplePie
    • What Constitutes ApplePie
    • NEVP DigitizationApparatus to Symbiota ingest mapping draft.
    • Administrative use case questions
  • Embedded Kepler
    • Decoupling Service layer from AccessPoint and Jobs (David's email)
    • Hello world
    • Source(s) for data for QC
  • Drivers (API documentation, MCZbase).
  • Progress on pubsubhubub implementation test.

Non-Tech

  • Annotations
    • Annotation MS
    • Task Group for Applicability Statement on OA
  • Collaborations
    • Specify/Symbiota
    • SCAN TCN
    • NEVP TCN

Reports

  • Paul
    • Circulated NEVP DigitizationApparatus to Symbiota ingest mapping draft.
    • Call with NEVP and TACC regarding image storage. Interest from TACC in obtaining specimen data with images, and maintaining currency using FP annotations.
    • Made Call with Bob to Jim Beach.
  • Maureen
    • Framed Administrative Use Case Questions:

Assuming we will have three separate programs to be installed: driver, client, "node"

  1. Who is expected to do installs? Sysadmins? Developers? Collection managers?
  2. Who deals with maintaining the software prerequisites (e.g. Glassfish)? Sysadmins? Developers? Collection managers?
  3. For the prerequisite software (e.g. Glassfish), will these components be available for use by other software, or are they private to Filtered Push?
  4. Obtaining the software: download from SourceForge? download from wiki?
  5. Does there need to be a GUI for the software installation?
  6. On what platforms will the software be installed?
  7. Updates: automatic? silent? roll back option? GUI? Do we create packages for particular flavors of Linux?
  8. How many installation processes are required per network?
  9. Who has access to install, configure, update, and "add capabilities?" Can this be done via web interface, or only by access to the machine?
  10. How does one discover and add "capabilities?" Can capabilities be removed?
  11. Will all network members be known at install time? Can new members be added later? Can members be removed?
  12. Do we need to be able to move an installation from one machine to another? Do we need to have a mirror set up at install time? Do we need to have a way to export data? Do we need to have a way of selectively exporting data, or is it an all-or-nothing thing?
  13. Backwards compatibility?
  14. Will the three different programs (client/driver/node) need to always operate with every version of each other program?
  15. Do we need to support removing annotations? For example, if someone wants to demonstrate how to use the software and puts in a "fake" annotation, do we need to be able to support removing single annotations? Do we need to support removing annotations made during a particular time frame? Do we need to support "trial runs," purging data used during an initial training period?
  16. What would be involved in uninstalling the software?

Notes

FilteredPush Team Meeting 2012 Nov 21 Present: Bertram, James, Heather, Maureen, Bob, Paul, David, Tianhong, Jim Agenda

  • Annotations
    • Progress on: Rewriting examples/rules from AO/AOD to OA

Bob: All the examples are rewritten. Not all of the rules have been redone, some have no implementation yet, building a test regimen for parsing/validating. All rules with current implementations have been rewritten.

David: Updated XSLT to display new georeference annotations in arbitrary clients.

Paul: Discussion yesterday about adding client helper component that allows validation of an rdf/xml document against rules.

David: have started on this with a parser - can validate and can identify rule based typing that applies to an annotation document.

Paul: Components for client helper tools thus: Construct rdf/xml annotation document, valdiate/parse rdf/xml annotation document against rules, sign rdf/xml document, facade for submission to a network (lightweight annotation system, and FP-access point).

Bob: Rules and things complient to them have tight coupling to constants and terminology. Tests may help in identifying overly tight coupling.

Bob: OA has added ability to discuss both composites and individual items.

  • ApplePie
    • What Constitutes ApplePie

James: In proposal, didn't name players. No letters of support. Inside budget justification have bit about servers. Discussion last week set up framework.

At what point should we start approaching people?

Maureen: Has started up framework for discussion of what is involved. James: Rich Rabler would like to deal with exccicati (published reference set of specimens, common in lichens and bryophytes, in essence standardized published duplicate set) with FP mechanisms.

Bob: Is key that it is a set?

James: Yes. Issue is there are problems in where to put the data (e.g. publication related information), with poor fit to darwin core concepts. Rich very happy to participate in this.

Maureen: Would be good to collect from Rich feedback on what is the problem with current handling of Exccicatti.

James: Have some from him, will put into a page. Discussion: Things to explore with clustering of information related to collection objects, localities, expeditions, etc.

    • NEVP DigitizationApparatus to Symbiota ingest mapping draft.

Maureen: What do we need to do with these?

Paul: Document for primary digitization apparatus, probably just look at. Larger symbiota document, we should consider implications for framing this as a new occurance record annotation.

    • Administrative use case questions

Maureen: have framed.

To be put into wiki page for commentary.

  • Embedded Kepler
    • Decoupling Service layer from AccessPoint and Jobs (David's email)

David: From experience with Hello World FP-medium, architecture is not very service oriented, to deploy hello world service need to package with the entire system, can't deploy as a separate service. Also coupling of service with jobs. Email dealt with methods to decouple:

Service layer (messaging, knowledge, analysis), should not need to know about the node. Use service descriptions instead of injecting EJBs into concrete jobs. Tight coupling to Java-EE, can't easily link in a sparql endpoint.

Jobs- buisness logic layer. Shouldn't need to modify API code, should be decoupled from services (can compose jobs in service layer).

Can have small services - allowing one component to compose with another. Example: Access point test is a test of everything - not separate test of say messaging.

David: Authorization of access to services, and encryption of data traversing services both standard problems. We should be able to get these by configuration with appropriate software.

    • Hello world

Bertram: High level: Modified version of kuration workflow to run on current data structure.

Paul: Perhaps should think of preprocesing to fit kuration configuration and extend configuration if needed to add new fields, rather than adding new configurations and actors for subsets of the same domain.

Bertram: One of points of struggle is how to start kepler. New build system that builds kepler into a single jar, allowing packaging, moving forward to integration.

    • Source(s) for data for QC

Paul: Able to access the Symbiota MySQL backend data.

Sven: Yes have been able to access.

  • Drivers (API documentation, MCZbase).

Meeting with Brendan set up for next week.

  • Progress on pubsubhubub implementation test.

Maureen: Working on how to convert an annotation into a document that Fedora can ingest.

Paul: Metadata question?

Maureen: Fedora can't take just arbitrary XML document. Question is all about how to retrieve the document later. Non-Tech

  • Annotations
    • Annotation MS

Still in Paul's court.

Bob: Working on getting Audubon core out this weekend.

    • Task Group for Applicability Statement on OA

Still in Paul's court.

  • Collaborations
    • Specify/Symbiota

Paul and Bob had call with Jim Beach. They will continue to maintain the back end in ways that we will be able to use. They do expect one more major release of Specify6 thick client (additional image support, some changes to database schema).

    • SCAN TCN
    • NEVP TCN

Call next week starts at 2PM Eastern. Burndown plan on agenda.