Features

#List of Features

##Developer Support

• Support for application branding
• Global, customizable theme support
• MVC-style architecture supporting reusable components
• Plugins, support custom UI components without need to edit core application
• Support application configuration via JSON(YAML??) file

##Loading/Population of mdEditor

###Formats

• Required
  • ADIWG JSON
  • mdEditor Native JSON
• Desired
  • ScienceBase JSON
  • XML
    • ISO-19115-2
    • ISO-19115-1
    • FGDC CSDGM
    • This will require parsing the XML by:
      • Client-side Javascript library (preferred)
      • Ajax request to an external service

###Methods

• Required
  • User loads an existing metadata record (partial or complete) into the online mdEditor by from their local machine.
    • Form upload
    • Drag-n-Drop
• Desired
  • User loads an existing metadata record (partial or complete) by providing a URL
  • Generate report that identifies which elements were not mapped/transferred upon import

##Output of mdEditor

###Formats

• Required
  • ADIWG JSON
  • mdEditor Native JSON
  • XML
    • ISO-19115-2
    • This will require generating the XML using the mdTranslator
• Desired
  • ScienceBase JSON
  • XML
    • ISO-19115-1
    • FGDC CSDGM
    • This will require generating the XML using the mdTranslator

###Methods

• Required
  • User save/exports a stand-alone metadata file to their local system.
• Desired
  • User save/exports a stand-alone metadata file via an external webservice.

##General User Interface

• Layout
  • Support collapsible components, e.g. optional or more complex sections.
  • Support highlighting of required and/or important elements.
  • Support for default field values where appropriate.
• Help
  • Support inline tooltips to inform users how particular elements in the mdEditor should be populated.
  • Identify mandatory fields/sections.
  • Support for context-sensitive documentation
  • Comprehensive user/developer guides(via GitBook?)
• Workflow
  • Support for user selectable configuration templates, e.g. project, data, spatial, etc.
  • Capture relationship between metadata records, i.e. project <=> data.
  • Support reuse of elements, e.g. contacts, that occur multiple times within a record
  • Support saving/restoring application state.
  • Guided "Metadata Wizard"
  • Support for offline use
  • Dynamically validate against the ADIWG JSON schema to assess for completeness/compliance.
  • Dynamic feedback about "metadata quality" based on configurable metrics

##Web Services

• Support GCMD Keyword web service, implementation examples here and here.
• Support for Contact webservice
  • Per instance configuration, point the mdEditor at your Contacts service.
  • Defined API for compatible webservice
• ITIS support
  • Taxonomic section ‘auto build’ from ITIS service, see here
• Tool provides feature to auto-build spatial reference/extent section of ADIWG JSON record? A user points to an ESRI supported dataset and .prj and spatial extent are read in and written into the correct elements/structure.