AtoM CSV Export Fields & DB Tables/Fields

41 views
Skip to first unread message

Elissa Sperling

unread,
Feb 14, 2023, 1:38:03 PMFeb 14
to AtoM Users
Hi, I'm looking at the AtoM DB ERD and I'm looking at some CSV exports and I would like to know the exact mapping from DB table fields to CSV export field. I'm waiting for our system admin to perform a data dump, so I can get a better sense of how the DB is populated, but either way the DB field to CSV field mapping would be helpful. I tried looking through AtoM documentation to see if I can get a better sense of what is happening backend, but I didn't find it immediately, so I thought I would ask here. So, either an export field = dbtable.dbfield kind of mapping and/or the SQL queries that go into the export. Hope that makes sense. Thank you!

Dan Gillean

unread,
Feb 14, 2023, 4:10:52 PMFeb 14
to ica-ato...@googlegroups.com
Hi Elissa, 

A per-field breakdown is a bit of work that I'm not sure that  when our team might have time to assemble for you, but I can at least provide some high-level info that might help get you started: 

All main entities have an entry on the object table, which is where they get their ID. This object ID value is typically used as the key to link entities across tables. 

The main data on a description export will come from the information_object and information_object_i18n tables. Note fields - of which there are a few in ISAD, more in DACS, and a LOT in the RAD template - are in their own separate table, so take a look at note and note_i18n.

Other related entities linked to the description will have entries on their own primary tables - so for example, you'd find linked subject access points on the term and term_i18n tables, the linked archival institution on nthe repository and repository_i18n tables, related authorities and name access points on the actor and actor_i18n tables, etc...

If the description was first created via an import, then the sourcename (a parameter that can be passed during a CLI import - or else it defaults to using the filename of the CSV) and the legacyID values from the original import will be stored in the keymap table. 

I would suggest that you take a look at some of the example queries on this page, which may also help: 
Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056
@accesstomemory
he / him


On Tue, Feb 14, 2023 at 1:38 PM Elissa Sperling <elissas...@gmail.com> wrote:
Hi, I'm looking at the AtoM DB ERD and I'm looking at some CSV exports and I would like to know the exact mapping from DB table fields to CSV export field. I'm waiting for our system admin to perform a data dump, so I can get a better sense of how the DB is populated, but either way the DB field to CSV field mapping would be helpful. I tried looking through AtoM documentation to see if I can get a better sense of what is happening backend, but I didn't find it immediately, so I thought I would ask here. So, either an export field = dbtable.dbfield kind of mapping and/or the SQL queries that go into the export. Hope that makes sense. Thank you!

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/ae5059fe-57ee-4192-a8b0-3788c12f8f9dn%40googlegroups.com.
Reply all
Reply to author
Forward
0 new messages