Concerning the changing of templates for an object: I would like to see the selected template for an object be something that generally isn't changed once set, but I also don't want to be limited to viewing the object's data in only that template.  I'd be happier having a coin's information displayed using the coin template (which for PAHMA would contain all of the fields that are commonly used for an object type, but which would not contain all of the fields that could *ever* be used for an object type), and if you're a curator or registrar who wants/needs to see absolutely everything about an object, you can *temporarily* (i.e., for this user during this session) switch to viewing the data in another layout/template.

Concerning selecting the appropriate template for an object: I wouldn't use collection, at least not for PAHMA, and I can't think of any other pre-existing field in the PAHMA implementation that would work for automatically assigning templates.  For new cataloging, of course, the registrar or other cataloger would manually select the appropriate template.  For existing records, I fear that template selection will probably end up being at least semi-manual.

Regarding Chris' example of creating a "Coin" record: How does CSpace know that you're creating a coin record other than Create New using Coin Template?  I think I'm missing something here, unless he's thinking of a different interface for creating new cataloging records.  For existing records that aren't [yet] assigned a template, I think it would be an awfully handy thing to have CSpace somehow realize that an object is of a certain type (perhaps via the objectName mapped against an ontology?)  and then suggest (or provisionally assign) the most appropriate template.  And if there's no appropriate template, leave it assigned to the default template.

+1 for that from PAHMA.

Hi Patrick, Concerning the changing of templates for an object: I would like to see the selected template for an object be something that generally isn't changed once set, but I also don't want to be limited to viewing the object's data in only that template. I'd be happier having a coin's information displayed using the coin template (which for PAHMA would contain all of the fields that are commonly used for an object type, but which would not contain all of the fields that could *ever* be used for an object type), and if you're a curator or registrar who wants/needs to see absolutely everything about an object, you can *temporarily* (i.e., for this user during this session) switch to viewing the data in another layout/template. Concerning selecting the appropriate template for an object: I wouldn't use collection, at least not for PAHMA, and I can't think of any other pre-existing field in the PAHMA implementation that would work for automatically assigning templates. For new cataloging, of course, the registrar or other cataloger would manually select the appropriate template. For existing records, I fear that template selection will probably end up being at least semi-manual. Regarding Chris' example of creating a "Coin" record: How does CSpace know that you're creating a coin record other than Create New using Coin Template? I think I'm missing something here, unless he's thinking of a different interface for creating new cataloging records. For existing records that aren't [yet] assigned a template, I think it would be an awfully handy thing to have CSpace somehow realize that an object is of a certain type (perhaps via the objectName mapped against an ontology?) and then suggest (or provisionally assign) the most appropriate template. And if there's no appropriate template, leave it assigned to the default template. Michael On Apr 13, 2012, at 12:39 PM, Patrick Schmitz wrote: > Can you guys respond to this thread, and my comments to ChrisT? I lost the > email, but it is archived here: > http://lists.collectionspace.org/pipermail/talk_lists.collectionspace.org/20 > 12-April/000716.html > > Am concerned about the Inventory case etc., when we would have to change a > template. > > Patrick > > -----Original Message----- > From: Chris Thompson [mailto:chris.at.walker@gmail.com] > Sent: Monday, April 09, 2012 2:42 PM > To: Patrick Schmitz > Subject: Re: [Talk] Edit Cataloging Templates > > This sounds pretty complicated. I would challenge the idea that a template > would be need to be changed. If something is missing from the "Coin" > template, then it should be added to the "Coin" template. > If there is a lot of rarely used fields, then they should be hidden by > default. The question I'd investigate is: What is the variable that should > be used to decide the template. Is it collection? or is it a user-definable > variable? Whatever it may be, I'd like to be able to create a template that > is selected by default when a user says: I want to create a "Coin" record, > and I don't have to do anything but name my template accordingly. Bonus: If > that template doesn't exist, then the default is used. What do you think? > > - Chris Thompson > > On 04/09/2012 03:02 PM, Patrick Schmitz wrote: >> The idea we have been discussing so far is that when an object is >> created, we would store the name of the template used to create it, >> inside the object. >> >> Then, when editing that object, we would check that field and load the >> referenced template, to edit it. >> >> The UI could *almost* do this now, but I need to talk to Yura about >> the order of calls in PageBuilder.js, to see what it would take to >> make this work. >> >> This means that the template name would be stored per-object. This >> functionality would be supported for any type of object, procedure, >> authority item, etc. >> >> There is a related feature we have discussed as possibly being needed: >> When editing an object, people may wish to switch to another template. >> This would allow them to switch from an Inventory template to a full >> cataloging template. I would constraint this to only be allowed if the >> current record has not been changed (don't want to deal with unsaved > data). >> >> Am not sure if this additional feature should also include support to >> "reset" the saved template. I presume so. But, does the user get to >> decide whether or not to save the new template as the default one for >> that object record? >> >> Some use-cases to consider: >> >> Case 1: I create an object with the Inventory template, and later want >> to add more cataloging info. When I am doing this additional >> cataloging, I probably want to save the cataloging template as the new >> default, rather than leaving the Inventory template as the default. >> >> Case 2: I create a coin object with the "Coin" template. I want this >> view to stay with the object. Later, someone wants to look at the coin >> using the default full cataloging template. They probably do not want >> to save the coin with the full cataloging template - it should stay >> associated with the coin template by default. >> >> Patrick >> >> >> >>> -----Original Message----- >>> From: talk-bounces@lists.collectionspace.org >>> [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Michael >>> T. Black >>> Sent: Monday, April 09, 2012 12:47 PM >>> To: Chris Thompson >>> Cc: talk@lists.collectionspace.org >>> Subject: Re: [Talk] Edit Cataloging Templates >>> >>> Hi Chris, >>> >>> +1 for that from PAHMA. >>> >>> Michael >>> >>> On Apr 9, 2012, at 12:34 PM, Chris Thompson wrote: >>> >>>> Here at the Walker we'd like to be able to use different >>> edit cataloging templates for different types of objects. >>> Patrick mentioned that there has been some talk about this, so here >>> is a bump. >>>> What we would like to see is a template per collection, so >>> maybe instead of CatalogingTemplate.html being the default, it would >>> be CatalogingTemplate-{object.collection}.html, or something like >>> that. >>>> - Chris Thompson >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collecti >>> o >>>> nspace.org >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org >>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.c >>> ollectionspace.org >>> > >