ENGAGE-369: The My Collection markup spout makes museum-specific assumptions about the structure of raw artifact documents

Metadata

Source
ENGAGE-369
Type
Sub-issue
Priority
Blocker
Status
Closed
Resolution
Won't Fix
Assignee
Svetoslav Nedkov
Reporter
Colin Clark
Created
2010-02-10T12:33:27.000-0500
Updated
2017-12-22T09:44:27.953-0500
Versions
  1. 0.1
  2. 0.3b
Fixed Versions
  1. 0.3
Component
  1. My Collection

Description

The My Collection server-side code makes a fatal assumption about the format of artifact data, and is hard-coded to only work with McCord's data.

This is, ultimately, due to ENGAGE-368, where we have incorrectly boxed up transformation logic in standard Couch views. Since My Collection uses a lucene view, it ends up returned artifact documents in a different format than the standard view.

We'll have to live with this bug for Engage 0.3b, but we need to completely rewrite the whole Engage mapping layer soon, as documented in ENGAGE-367.

Comments

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

    The repository has been archived.