Accession Number Parts Are Rearranged In URIs Sporadically

[kateblanch]

I'm not sure why this is (perhaps it's intentional), but the accession number value, which has become the object URI has it's parts rearranged in certain cases. This seems problematic to me in terms of consistency, but if it's a non-issue, that's ok too!

- Rearranged Parts:

• http://data.americanartcollaborative.org/acm/object/1_p2013/acc_no http://www.w3.org/1999/02/22-rdf-syntax-ns#value "P2013.1"
• http://data.americanartcollaborative.org/acm/object/25_p2013/acc_no http://www.w3.org/1999/02/22-rdf-syntax-ns#value "P2013.25" .

- Not Rearranged Parts:

• http://data.americanartcollaborative.org/acm/object/1967_4_474/acc_no http://www.w3.org/1999/02/22-rdf-syntax-ns#value "1967.474.4" .
• http://data.americanartcollaborative.org/acm/object/2011_4/acc_no http://www.w3.org/1999/02/22-rdf-syntax-ns#value "2011.4" .

[bsnikhila]

I am using a library function that removes the dots in the accession number to make the URIs. The different units of the accession number are string sorted and then joined with an '_', which results in the parts getting rearranged.

[workergnome]

This could be problematic, since an accession number of 2001.4.6 and an accession number of 2001.6.4 would then end up with the same URI, if I understand what you're doing?

[kateblanch]

Thanks for the background info @bsnikhila...can the string sorting just be removed from the process or could a simple "replace" command be used instead? I understand the need to replace the dots.