James,

Others can (and should) correct me if I'm wrong, but I think it is generally a good practice to "clone" one of the existing tenants as a starting point for a new deployment.  You mentioned below that you're currently using the "core" tenant, so I'd suggest cloning the core tenant instead.  See this wiki page for more details: https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant

-Richard

From: Talk talk-bounces@lists.collectionspace.org on behalf of James Keeline james@keeline.com
Sent: Wednesday, June 08, 2016 9:31 AM
To: Talk
Subject: Re: [Talk] Want to implement a controlled list for Chinese dynasties for CSpace

Chris, thank you for this reply.  I am working in several areas at once, including hiding fields and data import.  This morning I was reminded of a simplified document of a list of the Chinese dynasties.

Xia Dynasty 夏朝                                  (c. 2000 – 1650 b.c.)

Shang Dynasty 商朝                              (c. 1650 – 1050 b.c.)

Zhou Dynasty 周朝                                  (c. 1050 – 256 b.c.)

Qin Dynasty 秦朝                                  (c. 221 BC–207 b.c.)

Han Dynasty 汉朝                                      (202 b.c. – 9 a.d.)

Three Kingdoms 三国                                      (221–265 a.d.)

Southern and Northern Dynasties 南北朝        (265–581 a.d.)

Sui Dynasty 隋朝                                                        (581–618 a.d.)

Tang Dynasty 唐朝                                          (618–907 a.d.)

Five Dynasties and Ten Kingdoms 五代十国  (907-960 a.d.)

Song Dynasty 宋朝                                      ­ (960–1279 a.d.)

Yuan Dynasty 元朝                                      (1260–1360 a.d.)

Ming Dynasty 明朝                                      (1368–1644 a.d.)

Qing Dynasty 清朝                      (1644–1912 a.d.)

Republic of China 中华民国                        (1912–1949 a.d.)

People’s Republic of China (PRC) 中華人民共和國  (1943–Today)

Contemporary 当代

We are not using Default Concepts vocabulary (taxonomy?) so it seems like a reasonable one to repurpose if that is a straightforward way to go.

I think that the name of the dynasty in the two languages will be enough.  Though, if I can include them in the line, I can probably add the year ranges too.

Is it best to add these manually with copy-paste (if so where) or should I be looking at some kind of XML to run through an import service (if so details and guidance).  As you can see, there are not very many so a copy-paste could be satisfactory.

Richard Millet indicated that the system does not have a lot of facility for picking a specific year and identifying a dynasty from that.  It is not an essential function.

Looking at the installation (done by a colleague), it appears that there is not a specific tenant set up (we will use core) to be used in the customization.  This should be my first step for this task, I think.

I shall appreciate any other help on this.  It is, unfortunately, one of several which I am trying to resolve today.

James D. Keeline

From: Chris Hoffman chris_h@berkeley.edu
To: James Keeline james@keeline.com
Cc: Talk talk@lists.collectionspace.org
Sent: Wednesday, June 8, 2016 9:10 AM
Subject: Re: [Talk] Want to implement a controlled list for Chinese dynasties for CSpace

Hi James,

You’ve probably already figured out that CollectionSpace is notoriously flexible, so there are several ways to accomplish what you’re trying to do!

Here’s what might be the simplest.  It assumes you are not using the Default Concepts vocabulary for anything and that you want to do the least amount of customization.  There’s a field on cataloging in the Object History and Associations field group called “Associated Concept”.

Add your dynasties to the Default Concept vocabulary.  You could add the Chinese character version of the name as a non-preferred term.  There are fairly straightforward ways to rename this vocabulary from “Default Concept” to something like “Dynasty”, but that could be extra credit.  From the Wikipedia page, it doesn’t look like there are any hierarchical relationships needed amongst terms but that is something you could add if it were important.  (I apologize for my lack of historical knowledge here!)  If you are using Default Concepts for something else (like materials), you might need to create an additional concept vocabulary.

On the Cataloging screen, you could easily rename the field “Associated Concept” to “Dynasty”.  A bigger step would be to relocate that field up into the Object Production section.

There are probably a dozen other ways to do this, but this would probably work fine.

Good luck,
Chris Hoffman
UC Berkeley

On Jun 7, 2016, at 9:03 PM, James Keeline <james@keeline.commailto:james@keeline.com> wrote:

The objects for the San Diego Chinese Historical Museum are often associated with a dynasty to get an estimate of the age.

They provided me with this Wikipedia link to the names of the dynasties, years, and Traditional Chinese versions of the names.

https://en.wikipedia.org/wiki/Dynasties_in_Chinese_history

As I understand it, this needs to be implemented as a controlled list and then we associate specific fields to that list.  I have not learned how to accomplish this.  Probably my searches of the Wiki documentation are not triggering the correct terms.

Which field seems most appropriate in Core?  This is usually used for Object production date but it could also refer to the subject of an object or its inscription.  I suppose that once the controlled list is made, multiple fields can be associated with it.

Most of the staff reads English primarily and some Chinese.  If it is possible to display / search against both character sets for the AJAX-style look-ups, that will be fine.  I don't think we need to display the years but it would be helpful if the system knew about them.

James D. Keeline
Contracting with the Balboa Park Online Collaborative
for the San Diego Chinese Historical Museum

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

When reading the documentation for hiding fields in the form, I saw that creating a clone of the tenant for the museum was a required step.  In a content management system (the other CMS), we often do this for templates and CSS files that will override the defaults.  The goal there is to prevent the customized material from being overwritten with a code update.
A question related to the Chinese dynasties is before me.  If I make inputs on the core tenant of the system through the web interface, will it get carried over to the cloned tenant which we'll probably call SDCHM (or lower case if preferred)?
I'd like to get the dynasties and the display/storage location information entered while we work out the structure of an acceptable object description XML from the legacy data.  We can discuss that here or outside the group per your preference.  Probably a new thread is called for on the object data import. James D. Keeline

  From: Richard Millet <richard.millet@lyrasis.org>

To: James Keeline james@keeline.com
Cc: Talk talk@lists.collectionspace.org
Sent: Wednesday, June 8, 2016 10:44 AM
Subject: Re: [Talk] Want to implement a controlled list for Chinese dynasties for CSpace

James,

Others can (and should) correct me if I'm wrong, but I think it is generally a good practice to "clone" one of the existing tenants as a starting point for a new deployment.  You mentioned below that you're currently using the "core" tenant, so I'd suggest cloning the core tenant instead.  See this wiki page for more details: https://wiki.collectionspace.org/display/DOC/Creating+your+new+tenant

-Richard

Thanks for all the great feedback/advice, everyone!

James - just wanted to make sure that you're clear on the difference between a controlled list and an authority/vocabulary from a UI perspective.

Controlled lists are generally short lists, the contents of which don't change too frequently, and for which you don't need much additional description to understand the terms. These appear as dropdowns in the UI for those doing data entry, and are edited via Administration > Term List Management.

Authorities are used to manage structured vocabularies where it's desirable to establish preferred terms, create hierarchies, and add contextual information to terms. These terms can be created via import or, as Chris noted, through the Create New screen or on the fly during data entry. Those fields in the UI that are linked to authorities are denoted by a small down-facing gray arrow.

Each authority can be comprised of one or more vocabularies. So, in the case of concept, you might have one vocabulary that consists of Dynasty names, another for Materials, and another for Techniques. Users may choose when creating new terms which vocabulary the term should be added to.

Happy to do a quick online walkthrough if that will help.

Thanks,

Megan

Megan Forbes
CollectionSpace Program Manager
megan.forbes@lyrasis.org
917.267.9676 Cell
meganbforbes Skype

From: Talk talk-bounces@lists.collectionspace.org on behalf of Chris Hoffman chris_h@berkeley.edu
Sent: Wednesday, June 8, 2016 1:38:08 PM
To: James Keeline
Cc: Susan STONE; Talk
Subject: Re: [Talk] Want to implement a controlled list for Chinese dynasties for CSpace

Hi James,

I added the Concept values using the Create New screen and selected the Concept radio button under Vocabulary Terms.  People can add terms on the fly when they are on Cataloging, but in that case they are only entering the display name. If they wanted to add other metadata about the term, they’d have to click on the term name under the Terms Used section on the upper right of the Cataloging screen.

Regards,
Chris

On Jun 8, 2016, at 10:23 AM, James Keeline <james@keeline.commailto:james@keeline.com> wrote:

Chris, thank you for making the sample entries.  I will provide screen captures to the museum and explain the differences.

The legacy system did not provide them with a lot of functionality beyond the basics.  It was an Access system, of course as I mentioned.

The goal is to make the system as simple as possible, knowing that they can later grow into the complexity offered if there is a need or desire to do so.

In looking at the entries they made in that old system, what I see a lot is the dynasty in English and then the Chinese Traditional afterward.  Here is an example I found in the export:

this gourd-shaped bottle is decorated with a handpainted scene from the famous Ming Dynasty masterpiece, Along the River During Qingming 清明上河图, painted with enamel

This suggests to me the expected usage in terms of reports but I will confirm that and suppose that it can be edited as needed.

To repeat my question, is this best done through the web interface under the Administration tab?  It appears that you probably did this to make the samples.

James D. Keeline

From: Susan STONE <sstone@berkeley.edumailto:sstone@berkeley.edu>
To: Chris Hoffman <chris_h@berkeley.edumailto:chris_h@berkeley.edu>
Cc: James Keeline <james@keeline.commailto:james@keeline.com>; Talk <talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org>
Sent: Wednesday, June 8, 2016 10:10 AM
Subject: Re: [Talk] Want to implement a controlled list for Chinese dynasties for CSpace

I agree with all of this, except that if you do use Concept, having the dates in the qualifier will probably be an appropriate output (for a label or something), that is, if the dates are fixed and agreed upon, as they should be for Chinese dynasties.

(But A.D. goes before the years, strictly speaking. Or C.E. after!)

Susan

On Wed, Jun 8, 2016 at 10:04 AM, Chris Hoffman <chris_h@berkeley.edumailto:chris_h@berkeley.edu> wrote:
Hi James, it sounds like you are right in the thick of things right now!

I agree with Susan Stone’s comments that the Chinese character version should probably be a variant (a.k.a. non-preferred term). You could put the date range in another field on the Concept Authority, such as Scope Note.  Your idea of putting all that information in the term name itself is interesting. You might try it, but I worry that the result will be very long and might not display nicely.

I created a couple test records on core

• crhtest1  http://core.collectionspace.org/collectionspace/ui/core/html/cataloging.html?csid=5d676683-7dd8-41a5-9894 : In Associated Concept you’ll see a term that includes the English name, the Chinese characters, and the years.  The field is very narrow in this display.  Ideally it would be widened.  The appearance in Terms Used (upper right below the Media Snapshot), looks pretty good.  You can see the term record at http://core.collectionspace.org/collectionspace/ui/core/html/concept.html?csid=a2c14f70-26db-4083-b7c0&vocab=concept
• crhtest2 http://core.collectionspace.org/collectionspace/ui/core/html/cataloging.html?csid=d4e5767a-0d09-460b-b371 : This uses a term that has the Chinese character version as a non-preferred or variant term.  The field is still too narrow. You can see the term record at http://core.collectionspace.org/collectionspace/ui/core/html/concept.html?csid=52cec9ff-a1bd-4cd9-8171&vocab=concept

One way to think about these two approaches is to consider what downstream outputs are needed, e.g., reports and/or web portals.  If you include all the information in the term name (English, Chinese, and time span), then you’ll always get all three values in your other outputs.  That could be very good or it could be very bad!

By the way, there is a way to configure the “disambiguation terms” that appear when you hover over a term display name. There’s no good documentation for this customization but there’s a note with some links go github:
(A representative example, demonstrating how to provide additional disambiguation values for Person authority terms. Relevant changes in GitHub, nearly all pertinent to this issue but including a couple of other mods to these two files: Demands.jshttps://github.com/cspace-deployment/ui/compare/17c799199609922ab86ac955f3c3f8e420508ed3...8954cef1481bb66a514d6c79a9938038404d53ea#diff-714e9329071299d64d5619470e4e4813L397 and core-messages.properties-overlayhttps://github.com/cspace-deployment/ui/compare/17c799199609922ab86ac955f3c3f8e420508ed3...8954cef1481bb66a514d6c79a9938038404d53ea#diff-655141d5980fac6ad76512eb766eb658L114)

In terms of entering these terms, I agree that it will be easiest to add these by hand (even with copy and paste). It’s almost certainly not worth developing an import job.

Hopefully I’m not distracting you from too many other tasks!
Chris

On Jun 8, 2016, at 9:31 AM, James Keeline <james@keeline.commailto:james@keeline.com> wrote:

Chris, thank you for this reply.  I am working in several areas at once, including hiding fields and data import.  This morning I was reminded of a simplified document of a list of the Chinese dynasties.

Xia Dynasty 夏朝                                  (c. 2000 – 1650 b.c.)

Shang Dynasty 商朝                              (c. 1650 – 1050 b.c.)

Zhou Dynasty 周朝                                  (c. 1050 – 256 b.c.)

Qin Dynasty 秦朝                                  (c. 221 BC–207 b.c.)

Han Dynasty 汉朝                                      (202 b.c. – 9 a.d.)

Three Kingdoms 三国                                      (221–265 a.d.)

Southern and Northern Dynasties 南北朝

Sui Dynasty 隋朝                                                        (581–618 a.d.)

Tang Dynasty 唐朝                                          (618–907 a.d.)

Five Dynasties and Ten Kingdoms 五代十国  (907-960 a.d.)

Song Dynasty 宋朝                                      ­ (960–1279 a.d.)

Yuan Dynasty 元朝                                      (1260–1360 a.d.)

Ming Dynasty 明朝                                      (1368–1644 a.d.)

Qing Dynasty 清朝                      (1644–1912 a.d.)

Republic of China 中华民国                        (1912–1949 a.d.)

People’s Republic of China (PRC) 中華人民共和國  (1943–Today)

Contemporary 当代

We are not using Default Concepts vocabulary (taxonomy?) so it seems like a reasonable one to repurpose if that is a straightforward way to go.

I think that the name of the dynasty in the two languages will be enough.  Though, if I can include them in the line, I can probably add the year ranges too.

Is it best to add these manually with copy-paste (if so where) or should I be looking at some kind of XML to run through an import service (if so details and guidance).  As you can see, there are not very many so a copy-paste could be satisfactory.

Richard Millet indicated that the system does not have a lot of facility for picking a specific year and identifying a dynasty from that.  It is not an essential function.

Looking at the installation (done by a colleague), it appears that there is not a specific tenant set up (we will use core) to be used in the customization.  This should be my first step for this task, I think.

I shall appreciate any other help on this.  It is, unfortunately, one of several which I am trying to resolve today.

James D. Keeline

From: Chris Hoffman <chris_h@berkeley.edumailto:chris_h@berkeley.edu>
To: James Keeline <james@keeline.commailto:james@keeline.com>
Cc: Talk <talk@lists.collectionspace.orgmailto:talk@lists.collectionspace.org>
Sent: Wednesday, June 8, 2016 9:10 AM
Subject: Re: [Talk] Want to implement a controlled list for Chinese dynasties for CSpace

Hi James,

You’ve probably already figured out that CollectionSpace is notoriously flexible, so there are several ways to accomplish what you’re trying to do!

Here’s what might be the simplest.  It assumes you are not using the Default Concepts vocabulary for anything and that you want to do the least amount of customization.  There’s a field on cataloging in the Object History and Associations field group called “Associated Concept”.

Add your dynasties to the Default Concept vocabulary.  You could add the Chinese character version of the name as a non-preferred term.  There are fairly straightforward ways to rename this vocabulary from “Default Concept” to something like “Dynasty”, but that could be extra credit.  From the Wikipedia page, it doesn’t look like there are any hierarchical relationships needed amongst terms but that is something you could add if it were important.  (I apologize for my lack of historical knowledge here!)  If you are using Default Concepts for something else (like materials), you might need to create an additional concept vocabulary.

On the Cataloging screen, you could easily rename the field “Associated Concept” to “Dynasty”.  A bigger step would be to relocate that field up into the Object Production section.

There are probably a dozen other ways to do this, but this would probably work fine.

Good luck,
Chris Hoffman
UC Berkeley

On Jun 7, 2016, at 9:03 PM, James Keeline <james@keeline.commailto:james@keeline.com> wrote:

The objects for the San Diego Chinese Historical Museum are often associated with a dynasty to get an estimate of the age.

They provided me with this Wikipedia link to the names of the dynasties, years, and Traditional Chinese versions of the names.

https://en.wikipedia.org/wiki/Dynasties_in_Chinese_history

As I understand it, this needs to be implemented as a controlled list and then we associate specific fields to that list.  I have not learned how to accomplish this.  Probably my searches of the Wiki documentation are not triggering the correct terms.

Which field seems most appropriate in Core?  This is usually used for Object production date but it could also refer to the subject of an object or its inscription.  I suppose that once the controlled list is made, multiple fields can be associated with it.

Most of the staff reads English primarily and some Chinese.  If it is possible to display / search against both character sets for the AJAX-style look-ups, that will be fine.  I don't think we need to display the years but it would be helpful if the system knew about them.

James D. Keeline
Contracting with the Balboa Park Online Collaborative
for the San Diego Chinese Historical Museum

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

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

Yes, any help to move this forward in a reasonable manner is appreciated by me.  
Since the Core tenant has not been cloned (I have a request pending with the sysadmin who installed the system), will I lose data I put into the site now (e.g. this dynasty info and storage/display locations)?  I have this question to Richard and I guess it is in his area but perhaps you know as well?
It appears that we can temporarily do things in the distributed Core tenant for our demo and move the data to the created Core tenant clone afterward.  Failing that, I'll have to recreate things in the new tenant. James D. Keeline

  From: Megan Forbes <megan.forbes@lyrasis.org>

To: Chris Hoffman chris_h@berkeley.edu; James Keeline james@keeline.com
Cc: Susan STONE sstone@berkeley.edu; Talk talk@lists.collectionspace.org
Sent: Wednesday, June 8, 2016 11:23 AM
Subject: Re: [Talk] Want to implement a controlled list for Chinese dynasties for CSpace

#yiv2617903730 #yiv2617903730 -- P {margin-top:0;margin-bottom:0;}#yiv2617903730 Thanks for all the great feedback/advice, everyone!
James - just wanted to make sure that you're clear on the difference between a controlled list and an authority/vocabulary from a UI perspective.
Controlled lists are generally short lists, the contents of which don't change too frequently, and for which you don't need much additional description to understand the terms. These appear as dropdowns in the UI for those doing data entry, and are edited via Administration > Term List Management.
Authorities are used to manage structured vocabularies where it's desirable to establish preferred terms, create hierarchies, and add contextual information to terms. These terms can be created via import or, as Chris noted, through the Create New screen or on the fly during data entry. Those fields in the UI that are linked to authorities are denoted by a small down-facing gray arrow.
Each authority can be comprised of one or more vocabularies. So, in the case of concept, you might have one vocabulary that consists of Dynasty names, another for Materials, and another for Techniques. Users may choose when creating new terms which vocabulary the term should be added to.
Happy to do a quick online walkthrough if that will help.
Thanks,Megan
Megan Forbes
CollectionSpace Program Manager
megan.forbes@lyrasis.org
917.267.9676 Cellmeganbforbes Skype

So far we have a clean install on our production server.  I have tested payloads against the online demo site (core.collectionspace.org).  I am putting systems in place to make it possible to install into production when they seem ready.
With Richard's help I have an XML payload for our Artists information.  I think the other people in out system (300 or so) will import OK with this method. James D. Keeline

  From: Chris Hoffman <chris_h@berkeley.edu>

To: James Keeline james@keeline.com
Cc: Megan Forbes megan.forbes@lyrasis.org; Susan STONE sstone@berkeley.edu; Talk talk@lists.collectionspace.org
Sent: Wednesday, June 8, 2016 1:43 PM
Subject: Re: [Talk] Want to implement a controlled list for Chinese dynasties for CSpace

Hi James,Talking with the Berkeley team right now.  If you clone the core tenant, it will NOT copy over any data currently in the core tenant.  Have you imported data already? We saw another question from you back on June 2 about importing person authority data.Thanks,Chris

On Jun 8, 2016, at 11:36 AM, James Keeline james@keeline.com wrote:
Yes, any help to move this forward in a reasonable manner is appreciated by me.  
Since the Core tenant has not been cloned (I have a request pending with the sysadmin who installed the system), will I lose data I put into the site now (e.g. this dynasty info and storage/display locations)?  I have this question to Richard and I guess it is in his area but perhaps you know as well?
It appears that we can temporarily do things in the distributed Core tenant for our demo and move the data to the created Core tenant clone afterward.  Failing that, I'll have to recreate things in the new tenant. James D. Keeline

From: Megan Forbes megan.forbes@lyrasis.org
To: Chris Hoffman chris_h@berkeley.edu; James Keeline james@keeline.com 
Cc: Susan STONE sstone@berkeley.edu; Talk talk@lists.collectionspace.org
Sent: Wednesday, June 8, 2016 11:23 AM
Subject: Re: [Talk] Want to implement a controlled list for Chinese dynasties for CSpace

Thanks for all the great feedback/advice, everyone!
James - just wanted to make sure that you're clear on the difference between a controlled list and an authority/vocabulary from a UI perspective.
Controlled lists are generally short lists, the contents of which don't change too frequently, and for which you don't need much additional description to understand the terms. These appear as dropdowns in the UI for those doing data entry, and are edited via Administration > Term List Management.
Authorities are used to manage structured vocabularies where it's desirable to establish preferred terms, create hierarchies, and add contextual information to terms. These terms can be created via import or, as Chris noted, through the Create New screen or on the fly during data entry. Those fields in the UI that are linked to authorities are denoted by a small down-facing gray arrow.
Each authority can be comprised of one or more vocabularies. So, in the case of concept, you might have one vocabulary that consists of Dynasty names, another for Materials, and another for Techniques. Users may choose when creating new terms which vocabulary the term should be added to.
Happy to do a quick online walkthrough if that will help.
Thanks,Megan
Megan Forbes
CollectionSpace Program Manager
megan.forbes@lyrasis.org
917.267.9676 Cellmeganbforbes Skype