If new record is created, it contains only the ID number entered into the auto-complete field. Data and relations are not copied over.

Folks,

Please take a look at CSPACE-5458 (http://issues.collectionspace.org/browse/CSPACE-5458), which outlines the functional requirements for structured objects (or, objects with components, or sub-objects...or whatever you'd like to call them!). This is the main new functionality planned for release 2.7, and the last major piece of functionality planned for release 3.0.

In short, the basic requirements are very similar to those currently in place for hierarchical vocabularies.
User can assign a parent record to an object record
User can assign a child record to an object record
User can view an object record's parent, child, or sibling records
Similar restrictions to those for hierarchical vocabs:
An object can have only one parent
User should be warned if object added as child already has a parent

There are open questions around the workflows and user interaction - please see the Jira and wireframes (attached to the Jira) for extended information. Please feel free to add comments and questions to the Jira, or to respond to this email with questions, suggestions for improvement, etc.

We are on a tight schedule here as we wind down 3.0, so please send your thoughts over soon!

Thanks so much,
Megan

--
Megan Forbes
Collection Manager

Museum of the Moving Image
36-01 35 Avenue  Astoria, NY 11106
movingimage.us  718 777 6800
Direct 718 777 6834

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi Megan,

Thanks for sending out this note!  This is really important functionality,
and we're looking forward to it.  I've asked some others on campus to look
at this as well, but I'll respond with some points that I think are
relevant to a few deployments here.

I suspect Interaction option 1 might be sufficient and even preferred here
for the following reasons:

• Patrick Schmitz warned me that Interaction option 2 (keyword search)
  would likely change how hierarchical relationships are managed in
  authorities to this model, and I think that would not be good.  Term
  completion works well for authorities.
• Option 1 allows users to create new sub-objects on the fly without
  having to create them in advance, which is good
• In collections with lots of data, e.g., PAHMA, doing a keyword search
  can be slow

A few related notes:

In the Jira, below the summary workflow for option 1, you write:

If new record is created, it contains only the ID number entered into the
auto-complete field. Data and relations are not copied over.

I assume, the relation between the object and sub-object are created.  A
nice-to-have here would be to use the settings for Create From New to bring
over the values into the sub-object (implementers can configure which
fields get copied over).  Probably too complicated for this round of work
though.

For PAHMA, we have implemented a javascript method on the Collection
Object screen to derive a sortableObjectNumber value which allows sorting
to happen nicely. We would need to do something different to accommodate
option 1 (a nuxeo event version of this or a database trigger).

In the wireframes, the first field in the upper left under Object
Hierarchy is just labeled "Object" .  Is that supposed to be "Broader
Object" or  "Parent Object"?  In the wireframes, it's not clear how you
would see the parent object if you are on a sub-object record.

I'm really thrilled to see that you're including the ability to specify
the Object component type relationship!

Thanks!
Chris

On Aug 16, 2012, at 1:14 PM, Megan Forbes wrote:

Folks,

Please take a look at CSPACE-5458 (
http://issues.collectionspace.org/browse/CSPACE-5458), which outlines the
functional requirements for structured objects (or, objects with
components, or sub-objects...or whatever you'd like to call them!). This is
the main new functionality planned for release 2.7, and the last major
piece of functionality planned for release 3.0.

In short, the basic requirements are very similar to those currently in
place for hierarchical vocabularies.

- User can assign a parent record to an object record


- User can assign a child record to an object record


- User can view an object record's parent, child, or sibling records

Similar restrictions to those for hierarchical vocabs:

- An object can have only one parent


- User should be warned if object added as child already has a parent

There are open questions around the workflows and user interaction -
please see the Jira and wireframes (attached to the Jira) for extended
information. Please feel free to add comments and questions to the Jira, or
to respond to this email with questions, suggestions for improvement, etc.

We are on a tight schedule here as we wind down 3.0, so please send your
thoughts over soon!

Thanks so much,
Megan

--
Megan Forbes
Collection Manager

Museum of the Moving Image
36-01 35 Avenue  Astoria, NY 11106
movingimage.us  718 777 6800
Direct 718 777 6834

Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org