json-cao

[jacobdgm]

OldCantus has a json-cao tool/API that we may want to implement.

• there exists a cao_concordance attribute for chants in NewCantusDB.
• https://cantus.uwaterloo.ca/json-cao/002685 (002685 is the cantus_id of a chant) returns a dictionary with the chant's one cao_concordance (the string "C E F") as the key and an integer as a value
• running Chant.objects.filter(cao_concordances="C E F").count(), I see that the number of chants with a CAO concordance of "C E F" is 149 (not 23, the number displayed at https://cantus.uwaterloo.ca/json-cao/002685)
• https://cantus.uwaterloo.ca/json-cao/830303 displays "no chants"
• https://cantus.uwaterloo.ca/json-cao/002622 -> {"E HR F":26}
• Chant.objects.filter(cao_concordances="E HR F").count() -> 173, so I assume that displaying counts is not what cao_concordances is supposed to do.
• trying navigating to https://cantus.uwaterloo.ca/json-cao/, I get a "No chants" message, trying several different cantus ids

In an email, Debra clarified what a CAO concordance is:
"CAO CHANTS ARE THOSE INCLUDED IN "Corpus Antiphonalium Officii" (a catalogue compiled in the 1970s by a scholar-monk). If a Cantus ID # begins with "00", then the next 4 digits are its CAO number. The chants that we have found since have different formats of numbering, so they will have no concordances in CAO.
Each of the letters in the concordance field corresponds to a manuscript. At one point a few years ago, I thought it was more useful to have these concordances in our "Cantus Index catalogue" rather than with the Cantus Database manuscript inventories. There is a list of them here (http://cantusindex.org/cao) - formatting is in question, since the letters are not explained here (I would have done it a little differently, I think ...). But anyways, the concordance letters are very useful to researchers studying early sources. It would be useful, for instance, to know all the chants in "C" or all the chants in "E". Or, it would also be useful to know that the chant you are looking at in whatever ms is ALSO in "C" or it's also in "E". Scholars can find uses for lots of different types of display, so this is all valuable, however it's presented."

[jacobdgm]

We're thinking of not implementing this one. In the same email, Debra said "I DON'T KNOW WHY YOU HAVE A JSON EXPORT FOR THIS. Maybe this was just for moving the data that one time, a few years ago?
I WOULD RATHER HAVE THE CAO CONCORDANCES LINKED WITH THE CANTUS IDs IN THE "CANTUS INDEX", AND IF ANYONE NEEDS THAT INFO THEY CAN GET IT THERE (RATHER THAN IN THE CANTUS DATABASE). I DON'T WANT TO STORE THEM TWICE."
So, closing due to the fact that it may have been implemented for a one-off event, and because it would be better if it were stored in CantusIndex, not CantusDB