Thank you Adam. For the sake of the authority files' readability, I think it is preferable for me to manually change the legacyoid in psql so as to reflect the concept labels rather than their conceptids, so I will keep doing as I have done so far. I would, however, suggest that you consider, for Arches 4, the option of assigning legacyoids = to labels by default when concepts are added via the RDM.
Best, Andrea On Tuesday, May 3, 2016 at 5:56:16 PM UTC+1, Adam Lodge wrote: > > Hi Andrea, > > I think I understand the issue. > > As you have seem to have already surmised, the concepts.legacyoid column > is intended to store concept_id’s as defined in the csv authority > documents. Separately, Arches populates every added concept record with a > system-generated UUID value in the concept_id field of the concepts table. > > However, when you add a new concept through the RDM interface, there is no > provided “legacy” concept_id to populate into the legacyoid field. > Therefore, in those cases, the system automatically populates the field > with the same UUID value as went into the concept_id field. In essence, > because a concept_id was never fed in, the system generated value is the > first one to exist. > > As a solution, I would recommend taking a note of the UUID that is > generated as you add concepts through the RDM. I believe the interface > labels it as “Arches ID”. Use that value as your concept_id within the > business data that you are trying to import to make it link to appropriate > concepts in the RDM. > > Best, > Adam > > -- > Adam Lodge > Geospatial Systems Consultant > Farallon Geographics > > On Tuesday, May 3, 2016 at 9:33 AM, [email protected] <javascript:> > wrote: > > Hello, > > I am a member of staff of the Endangered Archaeology project, replacing > Richard Jennings in his role as IT officer from the beginning of this > month. I am writing to report on an issue that we have been experiencing > when adding concepts to existing Collection nodes (E55s) in the RDM. It > would appear that, when saving the new concepts, these get correctly > populated in the concepts.values table of the database, but not in the > concepts.concepts table, where the conceptid of the new concept populates > both conceptid and legacyoid. This, in turn, results in us being unable to > bulk upload data containing these new concepts - until the legacyoids are > manually modified with psql queries (which is what I have been doing so > far). > > Any idea as to why this happens? > > Thanks, > > Andrea Zerbini > Postdoctoral Research Associate > EAMENA, University of Oxford > > -- > -- To post, send email to [email protected] <javascript:>. To > unsubscribe, send email to [email protected] <javascript:>. > For more information, visit > https://groups.google.com/d/forum/archesproject?hl=en > --- > You received this message because you are subscribed to the Google Groups > "Arches Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] <javascript:>. > For more options, visit https://groups.google.com/d/optout. > > > -- -- To post, send email to [email protected]. To unsubscribe, send email to [email protected]. For more information, visit https://groups.google.com/d/forum/archesproject?hl=en --- You received this message because you are subscribed to the Google Groups "Arches Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
