Hi Jane,
When you say "index entries", are you referring to a
<persname> occurring within a <controlaccess> section?
As far as I can tell, the ICA-AtoM EAD import mapping doesn't
include <indexentry> or <index> tags.
You can stop importing <controlaccess><persname> tags by
adding a pound (#) character to
apps/qubit/modules/object/config/import/ead.yml
on each line from 152 to 155, as shown below:
# controlaccess_persname:
# XPath: "(controlaccess/persname |
controlaccess/controlaccess/persname)"
# Method: setActorByName
# Parameters: [$nodeValue, "$options = array('relation_type_id'
=> QubitTerm::NAME_ACCESS_POINT_ID, 'entity_type_id' =>
QubitTerm::PERSON_ID, 'source' =>
$importDOM->xpath->query('@source',
$domNode2)->item(0)->nodeValue, 'rules' =>
$importDOM->xpath->query('@rules',
$domNode2)->item(0)->nodeValue)"]
Please note that this means that
no name access points will
be created for personal names on import; There is no way to create a
name access point in ICA-AtoM without creating a corresponding
authority record.
Regards,
David Juhasz
P.S. I've CC'd this discussion to the Qubit developer list as well.
--
David Juhasz,
Software Engineer
Artefactual Systems Inc.
www.artefactual.com
On 12-01-12 04:02 AM, Jane Stevenson wrote:
We're testing out AtoM for the main UK archival aggregator, The
Archives Hub. My question is: Can we stop the automatic creation of
name authorities out of index entries as well as creator names when we
upload our EAD descriptions? It means that we get two name authority
entries for the creator, because they are always entered differently
in the indexes compared to the <origination> tag. Apart from anything
else, in the <origination> we don't add the life dates.
We can see the huge advantage of creating name authorities
automatically for all index terms, but often we have the same person
entered in several different ways in our data, as it is created by 200
different repositories, and so we would get several name authority
records for one person.