ENGAGE-250: Ensure all Engage-related components are correctly named and namespaced

Metadata

Source
ENGAGE-250
Type
Task
Priority
Major
Status
Closed
Resolution
Won't Fix
Assignee
N/A
Reporter
Michelle D'Souza
Created
2010-01-18T16:25:28.000-0500
Updated
2017-12-22T09:44:16.306-0500
Versions
  1. 0.1
Fixed Versions
  1. 0.3
Component
N/A

Description

Many of the Engage components and data feeds could be improved in terms of naming and namespacing. For example, the Artifact View component lives in the top-level fluid namespace and is called "artifact." Other components and data feeds should similar be reviewed and improved.

Attachments

Comments

  • Justin Obara commented 2010-02-05T15:35:37.000-0500

    Bug Parade Engage 0.3

  • Justin Obara commented 2010-02-24T13:15:32.000-0500

    The following components still need to be updated to use the engage name space

    Browse,
    Cabinet,
    Catalogue,
    NavigationList

    The following services still need to be updated to use the engage name space

    artifactView,
    browse,
    browseCatalogue,
    catalogue,
    codeEntry,
    exhibitionAbout,
    exhibitionBrowse (this is partially done),
    exhibitionView,
    collectionCommon,
    collectOperations,
    myCollectionService

  • y z commented 2010-03-17T10:46:44.000-0400

    This patch has everything up to date except for the names for catalogue and catalogue browse.

  • Justin Obara commented 2017-12-22T09:44:16.304-0500

    The repository has been archived.