ICA-ATOM fonctionalités

[Agnès Iskander]

Bonjour,

Nous avons intallés le logiciel ICA-ATOM et nous sommes entrain de le tester. Aussi nous aimerions savoir si certaines fonctionnalités pas encore développées dans la version 1.1 ou la 1.2 (prévue pour octobre 2011), seront prises en compte ultérieurement ou si, le périmètre est bien délimité ? concernant :

 

1) la gestion physique des documents :

- la gestion des magasins et du récolement feront-ils l'objet de futurs développements ? ICA-ATOM prend déjà en compte les unités de conditionnement (physical objects) à quand leurs localisations ?

- la communication et le prêt (j'ai vu cette réponse sur ce forum https://groups.google.com/group/ica-atom-users/browse_thread/thread/8eacfe56898f69cf?hl=en#

est-ce que cela signifie pour les futurs utilisateurs d' ICA-ATOM qu'ils doivent envisager les autres fonctionalités ailleurs (par des développements propres) ou bien, ces développements sont-ils envisagés par Artefactual beaucoup plus tard, et si oui dans quelle version ?   

 

2) la modification d'un masque de saisie de description archivistique

- par exemple : l'ajout d'un champ "notes confidentielles" <note AUDIENCE="internal"> sous le champ ISAD(G) 3.6.1 Notes

-ou bien des éléments avec des attributs EAD spécifiques.

 

3) l'ajout et le paramétrage d'un masque de saisie pour d'autres types de documents: les livres (books) et périodiques (serials)

- pour produire en saisie originale ou après import de notices bibliographiques

 

4) Pour les "taxonomies" et la gestion des autorités, y a t-il ou, y aura -t-il la fonction de fusionner deux entrées ?

exemple: fusion entre un nom de personne défini par un identifiant ARK (une donnée importée d'un référentiel) et le même nom sans identifiant (son doublon issu d'une migration de données originales), alors il devient nécessaire de nettoyer le fichier d'autorité: choisir l'autorité retenue et fusionner les descriptions liées.

 

5) la fonction de modification/suppression en lot sur un champ sans avoir à requêter en SQL dans MySQL ?

 

6) Quel convertisseur utilisent les usagers d'ICA-ATOM pour importer des données bibliographiques ? EAD ? MODS ?

 

7) Est-il possible d'ajouter/d'importer des "taxonomies" ou des données d'autorités venant de données bibliographiques ?

- par exemple les collections éditoriales <bibseries>

 

J'espère que vous pourrez me lire en français, s'il y a un doute demandez le en anglais, avec nos remerciements anticipés pour le complément d'informations.

 

Best regards,

 

Agnès Iskander

IMEC Collections. Administration de données

agnes.i...@imec-archives.com

www.imec-archives.com

 

 

[Evelyn McLellan]

Dear Ms. Iskander,

Thank you for your interest in ICA-AtoM. We have inserted answers to
your questions (in English) below.

Evelyn McLellan
MJ Suhonos

On Jun 28, 7:43 am, Agnès Iskander <agnes.iskan...@imec-archives.com>
wrote:

> Bonjour,
> Nous avons intallés le logiciel ICA-ATOM et nous sommes entrain de le tester. Aussi nous aimerions savoir si certaines fonctionnalités pas encore développées dans la version 1.1 ou la 1.2 (prévue pour octobre 2011), seront prises en compte ultérieurement ou si, le périmètre est bien délimité ? concernant :
>
> 1) la gestion physique des documents :
> - la gestion des magasins et du récolement feront-ils l'objet de futurs développements ? ICA-ATOM prend déjà en compte les unités de conditionnement (physical objects) à quand leurs localisations ?

> - la communication et le prêt (j'ai vu cette réponse sur ce forumhttps://groups.google.com/group/ica-atom-users/browse_thread/thread/8...

> est-ce que cela signifie pour les futurs utilisateurs d' ICA-ATOM qu'ils doivent envisager les autres fonctionalités ailleurs (par des développements propres) ou bien, ces développements sont-ils envisagés par Artefactual beaucoup plus tard, et si oui dans quelle version ?  

We are not planning to add active document management or lending
modules to ICA-AtoM. These are major functionalities that are not core
to ICA-AtoM, which is designed primarily to manage digital objects and
hierarchical descriptive metadata.

>
> 2) la modification d'un masque de saisie de description archivistique
> - par exemple : l'ajout d'un champ "notes confidentielles" <note AUDIENCE="internal"> sous le champ ISAD(G) 3.6.1 Notes
> -ou bien des éléments avec des attributs EAD spécifiques.

We interpret ISAD(G) 3.6.1 to be one note field only, although it is a
repeatable field which can contain many different types of
information. However, please note that we are planning to add an
accession module in release 1.2, scheduled for this Fall. You could
use the accession module fields to record a wide variety of
confidential information (such as donor information) about your
materials. Please see http://www.qubit-toolkit.org/wiki/index.php?title=Accession_module
for more information about the accession module.

>
> 3) l'ajout et le paramétrage d'un masque de saisie pour d'autres types de documents: les livres (books) et périodiques (serials)
> - pour produire en saisie originale ou après import de notices bibliographiques

ICA-AtoM currently provides ISAD(G), RAD (Rules for Archival
Description) Dublin Core and MODS templates for description. Please
note that the Digital Collection Builder, which is similar to ICA-AtoM
but is adapted for use in libraries, uses Dublin Core as its default
edit template (see http://dcb-gcn.canadiana.ca/), although it is easy
to switch to this template in ICA-AtoM as well (see the user manual at
http://ica-atom.org/doc/Default_templates). It is possible to develop
input templates for other kinds of materials using other standards
using a plug-in system in ICA-AtoM if you are comfortable working with
PHP code. See for example:
http://code.google.com/p/qubit-toolkit/source/browse/#svn%2Fbranches%2Fica-atom%2Fplugins%2FsfDcPlugin%2Fmodules%2FsfDcPlugin.
Also, we are always developing the software and may add more templates
in the future, depending on support and funding from the community.

>
> 4) Pour les "taxonomies" et la gestion des autorités, y a t-il ou, y aura -t-il la fonction de fusionner deux entrées ?
> exemple: fusion entre un nom de personne défini par un identifiant ARK (une donnée importée d'un référentiel) et le même nom sans identifiant (son doublon issu d'une migration de données originales), alors il devient nécessaire de nettoyer le fichier d'autorité: choisir l'autorité retenue et fusionner les descriptions liées.

At this time, it is not possible to automatically merge duplicate
terms within taxonomies and re-link the descriptions that are
associated with them. However, we welcome you to submit this as a
feature request with our online issue tracking system:
http://code.google.com/p/qubit-toolkit/issues/list.

>
> 5) la fonction de modification/suppression en lot sur un champ sans avoir à requêter en SQL dans MySQL ?

We have seen considerable interest in developing the ability to bulk
edit descriptions, and plan to introduce this feature in release 1.2.

>
> 6) Quel convertisseur utilisent les usagers d'ICA-ATOM pour importer des données bibliographiques ? EAD ? MODS ?

We use a system of XSLT for mapping various import standards such as
MODS and EAD to ICA-AtoM's internal data structure. Most archival
users perform their import using the EAD standard since that is the
one we are best able to support. Depending on the format of the data
you want to import, you might prefer to develop your own import XSLT
mapping.

>
> 7) Est-il possible d'ajouter/d'importer des "taxonomies" ou des données d'autorités venant de données bibliographiques ?
> - par exemple les collections éditoriales <bibseries>

For importing authorities, ICA-AtoM supports EAC (ISAAR) for authority
(ie. author / creator) records, and SKOS for importing terms /
taxonomies (ie. subject headings). If you wish to use another
standard such as MADS or MARC authorities, you will need to develop
your own import mapping (as explained in #6).
http://code.google.com/p/qubit-toolkit/source/browse/#svn%2Ftrunk%2Fapps%2Fqubit%2Fmodules%2Fobject%2Fconfig%2Fimport,
http://code.google.com/p/qubit-toolkit/source/browse/#svn%2Ftrunk%2Fdata%2Fxslt.


As you may know from your research, ICA-AtoM is free open-source
software and its development is founded upon the principles of
collaboration, sharing technical expertise and nurturing a community
of users and developers. Methods for getting new features developed
for ICA-AtoM include an institution funding Artefactual to develop a
new feature, which is subsequently released to the community of users
in the next version of the software; or gathering a number of user
institutions together to fund the development of a new feature, which
allows everyone to share in the cost and the benefits. For more
details, see: http://ica-atom.org/about.html

It also seems that some of the features that you are asking about are
typical of an integrated library system (ILS). You may want to have a
look at some popular open-source ILS to see if they are better able to
meet your needs:

http://www.open-ils.org/
http://www.koha.org/
http://koha-community.org/

>
> J'espère que vous pourrez me lire en français, s'il y a un doute demandez le en anglais, avec nos remerciements anticipés pour le complément d'informations.
>
> Best regards,
>
> Agnès Iskander
> IMEC Collections. Administration de données

> agnes.iskan...@imec-archives.comwww.imec-archives.com

[ziserman...@gmail.com]

Dear Mrs McLellan, 

I've red with great interest the answers you gave Mrs Iskander and find some answers to my own questions. I still have some however and was hopping that you could maybe help me. 

I'm currently working on a web based platform using AtoM to describe audiovisual archives. We intend to modify a bit the standard to make it more adjusted to audiovisual description needs. 

To do that, we intend to have a developer create a new default template, based mostly on ISAD(G)'s one, but with a few added fields. I've been reading some documentation on how to do that (https://www.ica-atom.org/doc/Descriptive_standards) and I've found some developing information for our developer. As far as I could tell, developing a new template consist of developing a new plugin. 

To be on the safe side, I would like to know if you have any documentation or advices for this upcoming development. 

Thanks so much for any advice you can have. 

Pauline Ziserman. 

[Dan Gillean]

Hello Pauline,

This sounds like an exciting development project!

Are you adding your own custom fields, or are you following any existing standards for the description of audio-visual materials? My first suggestion, if you are not already, would be to spend some time researching existing standards that can be used for the basis of a new template. AtoM as a project always tries to follow this development philosophy whenever possible, and if you develop a template based on an existing A/V standard, you could consider submitting the code to Artefactual afterwards, as this would certainly be of great interest to our user community. That way, we would review the code and make sure it meets our quality standards, and then incorporate it into a future public release, meaning that your institution would not need to maintain the plugin going forward, and you would be contributing your work back to the community.

We are currently working with a community partner to develop a VRA-Core template for AtoM which we hope to include in a future public release. Hopefully members of that institution, who are active on this list, might share some of their experiences and suggestions with you as well. For audio-visual materials, there are several approaches that could be taken that might follow a standards-based approach:

1) PBCore has seen revived use and growing adoption, especially since the release of its 2.0 schema in 2011

2) AudioMD and VideoMD are often used in conjunction with METS - and using METS would mean you could wrap existing EAD with AudioMD and VideoMD metadata. We would love to see a METS export for AtoM, as EAD could be wrapped with other elements not covered by EAD but still important to users. This would allow an AudioMD and/or VideoMD plugin to actually add a section to an existing ISAD(g) template, and export as METS (with AudioMD, VideoMD, and EAD embedded).

3)  FADGI has been working on a specification, so far called AS-07 for working with the MXF wrapper format for audio-visual preservation. Some more information on their activities here.

4) Existing standards may provide what you need - for example, PREMIS may include enough information that a PREMIS form for AtoM could be made, and a similar approach as suggested in 2) could be taken - a METS export option which wraps the preservation metadata with the descriptive EAD. Alternately, qualified Dublin Core may offer enough - in which case, you could develop our existing DC simple template into a fully-qualified DC template.

I'm not an audio-visual preservation expert, so surely there are other options out there of which I am not aware. If you are interested in pursuing a standards-based approach, you might try asking questions on the AMIA list-serv and other relevant lists.

I seem to recall that you've posted on our list before, and that you are working with AtoM 2, is that correct? If not, I would strongly recommend that you undertake any develop you'd like to see maintained going forward against AtoM 2, rather than ICA-AtoM. Check out our AtoM website for more information: https://www.accesstomemory.org/ Note that we have been rewriting all our end-user documentation for AtoM 2 as well - it is a work in progress, but you can see what we have done so far here: https://www.accesstomemory.org/docs/2.0/

If you are developing a new template, then yes, we could recommend that this be done in as modular a way as possible, by developing a new plugin for AtoM.

At Artefactual we use git, and GitHub for managing our code repositories - working with development branches is much simpler, and I definitely recommend using a similar service to manage your development project. You can explore our repo for AtoM here: https://github.com/artefactual/atom

The DACS template was the newest template added to AtoM, and was adapted from the ISAD(G) template - you might want to take a look at the initial git commit here, to get a sense of how it was added.

You'll find an overview of the technology stack that comprises AtoM here and here - I would strongly recommend that your developers be familiar with the Symfony 1.x framework, upon which AtoM was originally built.

If you do choose to contribute code back to AtoM, we have some basic guidelines on how to do so available here.

If you have any specific questions, feel free to post them on this list! Our developers and other members of the community will try to assist you. If you would like, Artefactual has also previously contracted remote developer tutorials via video-chat on an hourly basis, to assist developers familiarize themselves with the code base, and have an opportunity to ask an experienced AtoM developer questions in real-time. If this is of interest to you, please feel free to contact me off-list.

Keep us posted on how you choose to proceed, and how it goes. Best of luck!

Dan Gillean, MAS, MLIS
AtoM Product Manager / Systems Analyst,
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 http://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/9b4975d2-7b42-412a-ab9e-c175e6c26f66%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[maggie....@gmail.com]

Pauline

We have been entering audiovisual material into our ICA-AtoM database using the existing ISAD(G) template - we have a separate 'How to record audiovisual items' procedure which I have attached which you are welcome to review.

Maggie Shapley
University Archivist
ANU Archives (Noel Butlin Archives Centre, University Archives and Pacific Research Archives)
Menzies Building #2
Fellows Road
The Australian National University
Canberra ACT 0200 Australia

+61 2 6125 9602
maggie....@anu.edu.au
www.archives.anu.edu.au

[Pauline Ziserman]

Hello Dan, 

Thank you so much for this very complete answer !!! We have found many leads for our next moves. 

We are working on the second version of AtoM, and I've been comparing many audiovisual standards during the last few weeks : but I didn't know about PB Core and VRA Core so it will be a nice completion of the work we already started. 

Thanks also for all the technical information : I'll transmit that to our developer. Our template will not be based on one standard but will be an evolution of the ISAD(G) one, adapted to audiovisual needs, based on our comparison of other standards. We would be very happy to send you our code so that everybody can use it. 

I'll keep you posted on our project evolution. 

Thanks again, 

Pauline Ziserman. 

Never Lost Images. 

[Pauline Ziserman]

Hello Maggie, 

Thank you so much for your procedure document. It will be of great help. 

Pauline. 

Never Lost Images. 

[Jessica Bushey]

Thank you Maggie for sharing your procedural document with the AtoM Community. It is always interesting to see how our Users are implementing the software into their specific institutional scenario and workflows. 

All the best,

Jessica

---

Jessica Bushey, MAS
AtoM Product Manager

Systems Analyst
jes...@artefactual.com

Artefactual Systems Inc.
www.artefactual.com

--
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 http://groups.google.com/group/ica-atom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/df070bc2-215a-4661-8482-8eec8f50ddf9%40googlegroups.com.