Skip to first unread message

L Snider

unread,
Jul 17, 2016, 4:26:12 PM7/17/16
to ica-ato...@googlegroups.com
We had a recent ISAD(G) xml upload and found two issues. I have tried to test this out, but couldn't figure out why these things were happening:

The lower levels of the description were draft, but the higher level was okay and it published as usual. Have you heard of this happening before? Why would the draft happen?

The reference code for the children level of the fonds that was uploaded was duplicated. So if the reference code for the fonds should be XX-REPOS-001, at the file level we see XX-REPOS-001-001-1-1. For this issue, would this be because the inherit reference code is set to yes?

Thanks so much!

Cheers

Lisa


Dan Gillean

unread,
Jul 18, 2016, 10:21:23 AM7/18/16
to ICA-AtoM Users
Hi Lisa,

Regarding the publication status: it looks like you might be running into the following known issue:

It appears that lower-level descriptions are defaulting to the default publication status (set via Admin > Settings > Global).

I've added this ticket to a watch list so we can try to fix it for the 2.4 release - at this point we're finalizing the packaging for 2.3 so unfortunately it won't make it in. The good news at least is that in 2.3, publication status has been moved to the job scheduler, so you can publish large descriptive hierarchies asynchronously without the operation timing out in the browser. It's not a fix obviously but at least there's a way to reliably resolve it after import. The other workaround would be to temporarily change the default publication status prior to import, and then change it back after. In 2.3, you'll now find the option to update publication status under the More button menu, rather than in the edit template.

RE: the reference code - yes, it sounds like this is caused by the repository inheritance setting. I'm assuming that parent identifiers were manually included at lower levels (e.g. assuming there are no intermediate levels, the file-level identifier is 001-1-1-1), so you're getting the "001" from both the child record and inherited from the parent.

Cheers,


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

--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CA%2BmtHwb%2B8Y1%3DSOwN2ajOXDds94vYFD%2B8qgspkZbLR52%2BxDjaDQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

L Snider

unread,
Jul 20, 2016, 10:55:11 AM7/20/16
to ica-ato...@googlegroups.com
Hi Dan,

Thanks so much. I am going to do another test run after we update to 2.3 to see what I can do from there.

Cheers

Lisa

Reply all
Reply to author
Forward
0 new messages