Page Comparison

h6. User Story

Given an Object record, a user can choose a dimension aspect (e.g. "height" or "weight") and set dimensions for the object.

The User can specify, per the [Dimensions Schema]:

* The name of the part being measured (e.g. "overall", "base", "bicondylar length" \[for a femur bone\] ...)
* The dimension aspect being measured (e.g. "height", "width", "weight" ...)
* A dimension value (e.g. "6", "0.372")
* A value qualifier (free text that qualifies the value; e.g. "approximate" or a measurement of statistical deviation)
* A dimension measurement unit (e.g. "cm", "in", "g" ...)
* The date on which the dimension value was recorded.

Auto-conversion of dimension value:
* Conversion patterns may be defined by admin or by user
** imperial to metric, metric to imperial

* Value entered into dimension value field is converted, on-the-fly, to the corresponding dimension value
** inches to centimeters, kilograms to pounds, meters to miles, centimeters to inches, etc.
** Example: inches to centimeters: values entered Height = 27-7/8; Width = 36-3/4; converted to Height = 70.8; Width = 93.35

* Values may be entered with or without slashes and dashes to represent fractions. 
* Values will be stored with separators, dashes,  slashes, etc., for input and display.
** 41-3/8; 53-1/4; 21; 30 1/2

* Values may be entered using decimal points
* Values will be stored as decimals for sort and search
** 22.86; 27.94; 105.09; 135.26

Display version of Dimensions

* Need to add a field to Dimensions Schema for the 'Display' or 'Narrative' version of dimensions.  This is the version of dimensions that would go on a wall label, be used in a condition assessment, used for a loan agreement, used in an online presentation, etc.
** Examples: 38 x 30 x 6 in. (96.5 x 76.2 x 15.2 cm); 11 1/2 x 29 1/8 in. (29.21 x 73.98 cm); Tempera på træ, 78 x 48 cm;


* Auto-generate the display version of dimensions by concatenating the values input and the values converted.
* Suggested format =dimension part measured, dimension value, dimension measurement unit,  dimension qualifier)
* Examples: 38 x 30 x 6 in. overall (96.5 x 76.2 x 15.2 cm); 11 1/2 x 29 1/8 in. framed (29.21 x  73.98 cm);

This story is not about:
* Customizing or personalizing the names of parts presented to the user (such as "overall" or "base").
* Customizing or personalizing dimension aspects presented to the user (such as "height" or "weight").
* Customizing or personalizing dimension units of measurement.
* Associating dimension aspects with allowed units of measurement (e.g. "height can be expressed in mm, cm, meters, inches, or feet").
* Converting values between different units of measurement (for display purposes only).

Scope for implementation:
* For the Hello Mercury 0.4 release:
** -The scope of this user story is restricted to adding a- _{-}single{-}_ -dimension entry (e.g. one dimension "line" in the UI) per object record.-
** User may add information to three related fields: dimension, dimension measurement unit, and dimension value fields.
** Dimension and dimension value are both alphanumeric string fields
** Dimension measurement unit is a controlled list with values:

centimeters
millimeters
meters
liters
kilograms
cubic centimeters
minutes
carats
pixels
count
stories
inches
square feet
feet

* In a future (as yet-unspecified) release:
** Dimensions will be a multi-valued field, in which _multiple_ dimension entries - for multiple object parts ("overall", "base" ...) and aspects ("height", "weight" ...) can be applied to the Object record, and their values set.

Note that there are two types of dimensions that can be set:
* Overall dimensions
\\
and/or
* Dimensions for named parts

In the UI in the current Object Cataloging Wireframe (below), "overall" dimensions are intermingled with part dimensions, thus treating "overall" as just another instance of a named part, per [a decision by the Design Team at their July 10, 2009 meeting|Design Team Meeting Notes - July 10, 2009].

*See also*:

[Dimensions Schema]

[Measurement Requirements]

[Object Cataloging Wireframe|http://wiki.collectionspace.org/download/attachments/7208965/object_cataloging2.jpg], displaying a representative set of Dimensions (under "Object Description Information", then "Physical Dimensions").

[Services Team Design Meeting June 18, 2009], featuring an extensive discussion of dimensions.

h6. Related User Stories:



h6. Derived Stories:

{indent:1}

*Service Layer Stories*
{indent}
{indent:2}

Service Story: [Service consumer can add structured dimensions values to appropriate object, procedural and vocabulary/authority records|http://issues.collectionspace.org/browse/CSPACE-1348]



{indent}
{indent}

{indent:1}
{*}Application Layer Stories*
{indent}
{indent:2}


Application Story: <Describe a bit of functionality required by the UI layer components as clients.>
Related JIRA Task: <Link to a JIRA tasks at issues.collectionspace.org>


Application Story: <Describe a bit of functionality required by the UI layer components as clients.>
Related JIRA Task: <Link to a JIRA tasks at issues.collectionspace.org>
{indent}
{indent}

{indent:1}
{*}UI Layer Stories*
{indent}
{indent:2}

Related JIRAs:
* [http://issues.collectionspace.org/browse/CSPACE-632]
{indent}