Expected result: Index page of the selected description (2.)
Actual result: Create form with URL: http://demo.accesstomemory.org/informationobject/copy?
Possible fix (but I guess it the problem is somewhere else):
<li><?php echo link_to(__('Cancel'), array($resource->parent, 'module' => 'informationobject'), array('class' => 'c-btn')) ?></li>
<li><?php echo link_to(__('Cancel'), $sf_request->parent, array('class' => 'c-btn')) ?></li>
The "Add new" link inside the description/subjects/places page is for creating a hierarchy? If I am right why don't go back to a selected item after clicking "Cancel"
What I was expecting: Index page of selected item
Actual result: Browse page (index.php/subjects)
There is also a problem deleting descriptions with many children because the confirmation page has no paginator. I think this also happens with both AtoM versions:
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/a92064f8-7305-4924-a56c-5584b6fc218b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
What do you think about it?
So far as I know, USask is still interested in completing this development and contributing it to the public project, though I haven't heard any updates as to the status of this in a while.
As ever, we welcome pull requests if you would like to try implementing any of your suggestions! Let us know if you have any questions for our developers, they'll try to point you in the right direction if you're not sure how best to implement something.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/4c32f251-f8c3-40f9-9003-495100702ac8%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/b8d6bb71-a0e9-46e0-aebc-f45f35197b28%40googlegroups.com.
Typo inside csv file?:
The second item has 'en_fr' as content for scriptOfDescription. This should be 'en|fr' ?
It looks like the issue is that the value for the scripts needs to have leading uppercase (e.g. Latn not latn). En and fr are not a valid example of scripts at all. So if you use Latn, or Latn|Cyrl, script will import correctly. So will script of description, but it’s possible that field is not currently in the template (at least I don’t see it).
A related issue: if the incorrect value is imported, it looks like you need to edit the record twice before you can edit the script value. I’ve run into a similar issue (going back to 1.3), in this case for language, when the serialization is blank in the property.i18n table.
You received this message because you are subscribed to a topic in the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ica-atom-users/KTfkg4D43NE/unsubscribe.
To unsubscribe from this group and all its topics, 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/2755ba48-cf48-4358-a5ee-e4886fb2aa8b%40googlegroups.com.
... Only while it looks like I fixed the script field, I somehow neglected the scriptOfDescription in my corrections :(
As Tim noted, the value for the script of description should in fact be a 4-letter ISO 15924 script code, e.g. Latn, Cyrl, Copt, etc. I'm working on correcting this now - thanks for the catch!
In the process of doing so, I've also taken the time to add the field name and number from the related standard to each column value - so it will be a bit more useful for archivists doing mapping.
Once this PR is reviewed and accepted, I'll upload new versions to the wiki.
Thanks again for reporting this... not sure how I missed it the last time!
Regarding your other 2 reports, I've filed issues for them here: