ENGAGE-29: Generalize the artifact view component to work with different data

Metadata

Source
ENGAGE-29
Type
Sub-task
Priority
Major
Status
Closed
Resolution
Fixed
Assignee
Armin Krauss
Reporter
Michelle D'Souza
Created
2009-07-13T13:28:09.000-0400
Updated
2011-01-13T11:19:43.719-0500
Versions
N/A
Fixed Versions
N/A
Component
N/A

Description

Currently the artifact view component knows the exact format of the data that is imported into CouchDB from the example McCord data. This needs to be generalized to work with other formats of data.

Comments

  • Michelle D'Souza commented 2009-07-13T13:30:29.000-0400

    Implementing this may involve a lookup table for the model similar to the UI Spec used in collection space.

  • Armin Krauss commented 2009-07-14T14:33:31.000-0400

    I changed the artifact component so it has know knowledge about the data structure of the JSON used.
    A loadData.js script is at the moment pulling the JSON from the local file system and describing the path
    to the data in "lookup".

    I will commit this and the next step is to pull the data in loadData.js from the CouchDB. loadData.js will
    serve as an example how to call the artifact component

  • Armin Krauss commented 2009-08-07T11:06:19.000-0400

    The artifact.js file is not depending on the structure of the JSON file. Selectors can be used to
    tell the artifact.js where to expect data in the JSON