Project

General

Profile

Actions

Story #7040

open

A client side data and metadata manager and editor

Added by Chris Jones over 6 years ago. Updated about 6 years ago.

Status:
In Progress
Priority:
Normal
Assignee:
Target version:
Start date:
07/06/2016
Due date:
% Done:

35%

Estimated time:
(Total: 0.00 h)

Description

We want to be able to provide basic metadata management and data upload for researchers using a client-side app that is a replacement for the Metacat Data Registry (server-side Perl script.) This ticket is the container story for this work. We need to develop requirements, mockups, and use cases to convey the scope of the work before (and possibly during) development. Since this is a major change in both functionality and UI layout, we'll target this for a 2.0.0 release.

For development, we'll be extending the existing Backbone application with new classes that:

1) Support the creation and parsing of DataONE SystemMetadata,

2) Support the creation and parsing of OAI-ORE resource maps

3) Support the creation and parsing of EML science metadata documents

4) Support the future creation and parsing of ISO 19139 science metadata documents

5) Support the future creation and parsing of FGDC CSDGM science metadata documents

Design documents are being developed here: https://github.com/NCEAS/metacatui/blob/master/metacatui/docs/design/editor


Subtasks 43 (31 open12 closed)

Task #7041: Develop a design document to steer software development.ResolvedChris Jones07/06/2016

Actions
Task #7042: Develop mockup images for editor use casesResolvedChris Jones07/06/2016

Actions
Task #7043: Develop use case documents for basic editor functionsResolvedChris Jones07/06/2016

Actions
Task #7044: Develop the 'Upload Data' use caseClosedChris Jones07/06/2016

Actions
Task #7045: Develop the 'Rename a file' use caseClosedChris Jones07/06/2016

Actions
Task #7046: Develop the 'Remove a file' use caseClosedChris Jones07/06/2016

Actions
Task #7047: Develop the 'Add Metadata' use caseClosedChris Jones07/06/2016

Actions
Task #7048: Develop the 'Update Metadata' use caseResolvedLauren Walker07/06/2016

Actions
Task #7049: Develop the 'View Public Metadata' use caseResolvedLauren Walker07/06/2016

Actions
Task #7050: Develop the 'Add a Nested Dataset' use caseResolvedLauren Walker07/06/2016

Actions
Task #7056: Investigate schema-based JS object generationClosedChris Jones07/15/2016

Actions
Story #7106: Retrieve an EML doc and parse into model attributesNew09/30/2016

Actions
Feature #7107: Basic fields on the EML211 modelNew09/30/2016

Actions
Feature #7108: EMLParty modulesNew09/30/2016

Actions
Feature #7109: EMLKeyword modulesNew09/30/2016

Actions
Feature #7110: EMLOnlineDistributionNew09/30/2016

Actions
Feature #7111: GeographicCoverageNew09/30/2016

Actions
Feature #7112: TemporalCoverageNew09/30/2016

Actions
Feature #7113: TaxonNew09/30/2016

Actions
Feature #7114: EMLMethodsNew09/30/2016

Actions
Feature #7115: EMLProjectNew09/30/2016

Actions
Story #7116: Serialize an EML model to an EML documentNew09/30/2016

Actions
Story #7117: Serialize a System Metadata doc from a DataONEObject modelIn Progress09/30/2016

Actions
Story #7118: Create a new EML and its System Meta doc on a member nodeNew09/30/2016

Actions
Story #7119: Render an EML model in the UINew09/30/2016

Actions
Story #7120: Overview sectionNew09/30/2016

Actions
Story #7121: People sectionNew09/30/2016

Actions
Story #7122: Dates sectionNew09/30/2016

Actions
Story #7123: Locations sectionNew09/30/2016

Actions
Story #7124: Taxa sectionNew09/30/2016

Actions
Story #7125: Methods sectionNew09/30/2016

Actions
Story #7126: Projects sectionNew09/30/2016

Actions
Story #7127: Allow editing of EML displayNew09/30/2016

Actions
Story #7128: Make all fields in the EML View editableNew09/30/2016

Actions
Story #7129: Update EML module models when their view fields are editedNew09/30/2016

Actions
Story #7130: Update an EML doc and System Metadata doc on a member nodeNew09/30/2016

Actions
Story #7131: Allow users to edit or create data packages in the editorNew09/30/2016

Actions
Feature #7132: Serialize a Resource Map from a DataPackage collectionIn ProgressLauren Walker09/30/2016

Actions
Feature #7133: Rename a data object by updating its System Metadata (via DataONEObject model)Resolved09/30/2016

Actions
Story #7134: Remove a data object from a collectionNew09/30/2016

Actions
Story #7135: Show data upload form to the user in the DataPackage viewNew09/30/2016

Actions
Story #7136: Add a new data file to a packageNew09/30/2016

Actions
Story #7137: Create a data package from scratchNew09/30/2016

Actions
Actions #1

Updated by Lauren Walker over 6 years ago

  • Subject changed from A client side data and metadata manager and editor needs to be developed to A client side data and metadata manager and editor
  • Status changed from New to In Progress
Actions

Also available in: Atom PDF