talk@lists.collectionspace.org
WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org
View all threadsWant to implement a controlled list for Chinese dynasties for CSpace
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. KeelineContracting with the Balboa Park Online Collaborative for the San Diego Chinese Historical Museum
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.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 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.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
James,
I agree with Chris that the Chinese-character version of the dynasty should
be a variant term, because Chinese characters won't be intelligible to
everyone, and that therefore using the Concept authority would be the best
way to go. If you used a straight vocabulary, you could follow the
translation or transliteration with characters, or use characters with a
parenthetical gloss, but that wouldn't be as good.
Another good place to apply the concept authority to Date Era in one of the
structured date fields.
Let me know if you have other issues with Chinese-character data. I work
with it a lot (not necessarily in cspace).
Susan Stone
On Wed, Jun 8, 2016 at 9:10 AM, Chris Hoffman chris_h@berkeley.edu wrote:
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.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.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
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 HoffmanUC Berkeley
On Jun 7, 2016, at 9:03 PM, James Keeline 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. KeelineContracting with the Balboa Park Online Collaborative for the San Diego Chinese Historical Museum
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Susan, it appears that you are saying that for each taxonomy term that I shall want to separate out the English and Chinese versions. As long as this will work so that either term can be selected with the AJAX feature, that will be fine.
Is there a similar field (e.g. notes) that can be used to store the year information as I posted in my reply to Chris? This list is the simplified version the museum wishes to use.
If there is documentation I can follow for creating or editing this kind of vocabulary._____
Personally I don't read Chinese. However, in preparing the data for import, I have had to make sure that the characters are preserved in each step. To make my XML files for import, I have had to go from MS Access (the legacy system) to an export in Excel XLSX. From here I am storing the data in MySQL (properly set UTF8 charset and collation) so I can use PHP to compose an XML to be delivered to the import service.
I was able to get a test to work for a person with English and Chinese characters and send it to the online demo (core.collectionspace.org). Now I need to do the same for an object description. Several fields may include Chinese. If I can get one to work, I hope I can repeat the process for the roughly 2,000 objects. The legacy system has some 52 fields in its inventory table. Not all of them are easily mapped to CSpace and a few I think I know the adjacent XML element but not the required parent pieces. I am seeking documentation on this but it is eluding me.
Sometimes it seems as if I am doing things the hard way because there is not a direct approach. This is an area where experience with the system can make a huge difference. It is still rather new to me though I have been a LAMP (P=PHP) programmer for more than 16 years. James D. Keeline
From: Susan STONE <sstone@berkeley.edu>
To: Chris Hoffman chris_h@berkeley.edu
Cc: James Keeline james@keeline.com; Talk talk@lists.collectionspace.org
Sent: Wednesday, June 8, 2016 9:17 AM
Subject: Re: [Talk] Want to implement a controlled list for Chinese dynasties for CSpace
James,
I agree with Chris that the Chinese-character version of the dynasty should be a variant term, because Chinese characters won't be intelligible to everyone, and that therefore using the Concept authority would be the best way to go. If you used a straight vocabulary, you could follow the translation or transliteration with characters, or use characters with a parenthetical gloss, but that wouldn't be as good.
Another good place to apply the concept authority to Date Era in one of the structured date fields.
Let me know if you have other issues with Chinese-character data. I work with it a lot (not necessarily in cspace).
Susan Stone
On Wed, Jun 8, 2016 at 9:10 AM, Chris Hoffman chris_h@berkeley.edu wrote:
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 HoffmanUC Berkeley
On Jun 7, 2016, at 9:03 PM, James Keeline 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. KeelineContracting with the Balboa Park Online Collaborative for the San Diego Chinese Historical Museum
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
James,
The concept authority gives you a lot to work with so that you can separate
variant forms of a term. You have term qualifier, where you could put the
date ranges for a dynasty (though that wouldn't give you date range
searchability), and term type and term language where you could put things
like "translated term" and "transliterated term" if you modified the list
(which may or may not be advised).
For a controlled vocabulary field, I think it is better not to combine
different forms of a term in the same field if you can get away with it,
but it also may be simpler to have the combo form show up than to design
for the different versions.
It sounds like you've got the Chinese passing through from the older
system, so you are probably good to go.
Susan
On Wed, Jun 8, 2016 at 9:41 AM, James Keeline james@keeline.com wrote:
Susan, it appears that you are saying that for each taxonomy term that I
shall want to separate out the English and Chinese versions. As long as
this will work so that either term can be selected with the AJAX feature,
that will be fine.
Is there a similar field (e.g. notes) that can be used to store the year
information as I posted in my reply to Chris? This list is the simplified
version the museum wishes to use.
If there is documentation I can follow for creating or editing this kind
of vocabulary.
Personally I don't read Chinese. However, in preparing the data for
import, I have had to make sure that the characters are preserved in each
step. To make my XML files for import, I have had to go from MS Access
(the legacy system) to an export in Excel XLSX. From here I am storing the
data in MySQL (properly set UTF8 charset and collation) so I can use PHP to
compose an XML to be delivered to the import service.
I was able to get a test to work for a person with English and Chinese
characters and send it to the online demo (core.collectionspace.org).
Now I need to do the same for an object description. Several fields may
include Chinese. If I can get one to work, I hope I can repeat the process
for the roughly 2,000 objects. The legacy system has some 52 fields in its
inventory table. Not all of them are easily mapped to CSpace and a few I
think I know the adjacent XML element but not the required parent pieces.
I am seeking documentation on this but it is eluding me.
Sometimes it seems as if I am doing things the hard way because there is
not a direct approach. This is an area where experience with the system
can make a huge difference. It is still rather new to me though I have
been a LAMP (P=PHP) programmer for more than 16 years.
James D. Keeline
From: Susan STONE sstone@berkeley.edu
To: Chris Hoffman chris_h@berkeley.edu
Cc: James Keeline james@keeline.com; Talk <
talk@lists.collectionspace.org>
Sent: Wednesday, June 8, 2016 9:17 AM
Subject: Re: [Talk] Want to implement a controlled list for Chinese
dynasties for CSpace
James,
I agree with Chris that the Chinese-character version of the dynasty
should be a variant term, because Chinese characters won't be intelligible
to everyone, and that therefore using the Concept authority would be the
best way to go. If you used a straight vocabulary, you could follow the
translation or transliteration with characters, or use characters with a
parenthetical gloss, but that wouldn't be as good.
Another good place to apply the concept authority to Date Era in one of
the structured date fields.
Let me know if you have other issues with Chinese-character data. I work
with it a lot (not necessarily in cspace).
Susan Stone
On Wed, Jun 8, 2016 at 9:10 AM, Chris Hoffman chris_h@berkeley.edu
wrote:
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.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.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
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 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 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 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 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.js https://github.com/cspace-deployment/ui/compare/17c799199609922ab86ac955f3c3f8e420508ed3...8954cef1481bb66a514d6c79a9938038404d53ea#diff-714e9329071299d64d5619470e4e4813L397 and core-messages.properties-overlay https://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.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.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.com mailto: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 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.org mailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
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.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.js
https://github.com/cspace-deployment/ui/compare/17c799199609922ab86ac955f3c3f8e420508ed3...8954cef1481bb66a514d6c79a9938038404d53ea#diff-714e9329071299d64d5619470e4e4813L397
and core-messages.properties-overlay
https://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.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.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.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.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
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.edu>
To: Chris Hoffman chris_h@berkeley.edu
Cc: James Keeline james@keeline.com; Talk 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.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.js and core-messages.properties-overlay)
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.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.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 HoffmanUC Berkeley
On Jun 7, 2016, at 9:03 PM, James Keeline 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. KeelineContracting with the Balboa Park Online Collaborative for the San Diego Chinese Historical Museum
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
James,
What you show with the characters following the transliteration is commonly
used in text publications (or text fields in cspace). The question to ask
is whether vocabulary fields should be treated differently.
Susan
On Wed, Jun 8, 2016 at 10:23 AM, James Keeline 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.edu
To: Chris Hoffman chris_h@berkeley.edu
Cc: James Keeline james@keeline.com; Talk <
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.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.js
https://github.com/cspace-deployment/ui/compare/17c799199609922ab86ac955f3c3f8e420508ed3...8954cef1481bb66a514d6c79a9938038404d53ea#diff-714e9329071299d64d5619470e4e4813L397
and core-messages.properties-overlay
https://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.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.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.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.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org