Roadmap

The following features/fixes are planned for future versions of Wildbook.

Version 5.4.1

  • FIX: Measurements blank in OBIS export
  • NEW: support multiple location IDs in Simple CMR export
  • NEW: hide/show biological samples
  • NEW: hide/show relatives and relationships on individuals.jsp
  • NEW: Put path to servlet response template in commonConfiguration.properties
  • NEW: individuals.jsp page: set default zoom for map to a single value
  • NEW: change workflow state when setting individual ID from encounter.jsp
  • NEW: D3 visualization of co-occurrence in Individual Search
  • NEW: Upgrade DataNucleus 4.1 (underway)
  • MOD: Switch Encounter Search to use AJAX/GeoJSON code, consolidation with Individual Search mapping code

Version 6.0

  • MOD: Limit number results displayed for spot pattern matching (whaleshark.org)
  • NEW: Adoption endpoint servlet
  • NEW: additional social media link for Encounter, Marked Individual, occurrence: email this link to a friend
  • FIX: L10N ongoing cleanup of untranslated stragglers
  • NEW: Silo security (Full Release)
  • NEW: Storytelling part 2: Wildbook UI support
  • NEW: timeline display on individuals.jsp
  • NEW: Convert JSP-based UI to HTML5 and REST/JSON - Part 2
  • NEW: Convert SinglePhotoVideo to MediaAsset to support remote binary/blob data stores
  • NEW: Occurrence-based data submission
  • NEW: Make default map location on submission page configurable through commonConfiguration.properties
  • MOD: Improve batch upload support to allow for multi-file upload on Android devices if possible.
  • NEW: L10N support continued: some administration pages remain.
  • FIX: Delete a keyword even if it has dependent photos, but warn user about how many images have the keyword assigned.
  • NEW: Occurrence data and photo direct submission (apodstrandings.org)
  • MOD: Make “Find record” result a list of matches rather than going to only one match
    • NEW: Find Record field should be case-insensitive
  • NEW: Search Comparison should support n-number of side-by-side comparisons (geneGIS request)
  • NEW: commonConfiguration.properties wizard-based administration (geneGIS request)
  • NEW: Ability to view all communities
  • NEW: Support catalogs with individuals from multiple taxonomic families. Previously, we only varied on genus and species. (CaribWHALE)
  • NEW: First-run installer (GeneGIS)
  • MOD: Add a link to the SRGD file format specification from the Encounter Search export option for it (GeneGIS)
  • NEW: Encounter Search: extend haplotype and genotype from other encounters to encounter matching (geneGIS request)
  • NEW: Color code individual temporal paths in Individual Search if parameter individualID is used
  • NEW: localize text in servlets and EncounterQueryProcessor and IndividualQueryProcessor
  • NEW: support French language strings
  • NEW: Acoustic Tag → electronic tag and add type, such as VHF, UHF, acoustic (EWT)

Version 6.1

  • NEW: Survey object
  • NEW: User.allowVisibleEmailAddress
  • NEW: Location ID-based, map-based global dashboard
  • NEW: User.showProfile
  • NEW: Set Encounter.eventID
  • FIX: Fix tab sizing in Encounter Search results tabs, specifically Calendar
  • NEW: N-measurement display in occurrence.jsp
  • NEW: Support replicate sequence info (GeneGIS) – FASTA (http://en.wikipedia.org/wiki/FASTA_format)
  • NEW: Social Search function for Encounter Search
  • NEW: Add Encounter.sizeClass with Individual Search searchability
  • NEW: Add Encounter.dataSources[] attribute - affects menus, search, and documentation
  • NEW: In Encounter Search mapping, give the user the option of extending the haplotype to other encounters of the same MarkedIndividual (geneGIS request)
  • NEW: Add lat/long to GenAlEx output from Search Comparison (GeneGIS)
  • NEW: Add GenePop export to Individual Search (geneGIS request)
  • NEW: provide comprehensive developer documentation for other developers (underway)
  • NEW: Mapping biomeasurements (GeneGIS)
  • NEW: create additional wiki calls for the fields in encounter.jsp, occurrence.jsp and individuals.jsp, including dynamic properties
  • NEW: Multi-select scan tasks for deletion (Georgia Aquarium request)

Future feature requests/requirements

  • NEW: allow for self-registering JSP imports in encounter.jsp, individuals.jsp, occurrence.jsp, admin.jsp, and stats.jsp
  • MOD: do not send Individual ID email notifications until an Encounter is approved
  • NEW: Occurrence Search
  • NEW: allow shapefiles and KML files to include locales.properties values
  • NEW: Search on a range of measurement values in Encounter Search and Individual Search
  • Shift to pure HTML 5, especially FLASH pattern matching piece
    • Make the pattern-matching piece expand to full screen (Simon Pierce request)
  • allow for self-registering, self-describing export format servlets for Encounter and Individual Search
  • refactor two existing spot pattern recognition algorithms as patterning passport services
  • Remove spots as a database table and make them part of a patterning passport
  • allow JSON-based synchronization between Wildbook instances
  • add a third algorithm as a demo of the pluggable, Web Service interface
  • Support custom Keywords assigned to Encounter objects as open-ended and user-specified.
  • add style to GIS shapefiles
  • add taxonomy to GIS shapefiles
  • set search results order
  • interface for quickly adding new capture history export formats
  • replace DYnamic Image for thumbnail generation
  • Data set validation and error-checking tools:
    • list of individuals as both male and female, so they can be manually assigned to the correct sex where possible.
    • Where possible, direct measurements should be the default length measurements for each individual
    • For sharks where multiple length estimates are available, it would be good if there was a way of manually assigning one or more 'correct' lengths (ideally on a per-year basis) for use in automatic calculations as per the current statistics page. Where multiple submitters have estimated the length of a single shark the range can be all over the place - on one single shark from Mozambique I've noted length estimates ranging from 3 m to 9 m. It would be nice to be able to remove wayward measurements from the dataset.