Adding information objects via Institutions...

[Mike B]

Hi there,

We have an (anticipated) issue with the way adding ISAD(G) resources
and assigning them to institutions is done in ICA-AtoM 1.2.

As I understand it, the way adding resources currently works is that
you select Add -> Archival Description and then in the Context section
select the right Repository from the auto-complete list.

The problem with this is that we're going to be dealing with a lot of
Institutions (>1500), and some of them have very similar names.
There's not enough information in that auto-complete list to have
confidence that people will select the right one all the time.

The way I'd like it to work is that you'd navigate to the relevant
institution using the standard search functionality, and then, on that
institution's details page, choose "Add Holding" or whatever. This
would lead to a new ISAD(G) form with the repository information pre-
filled.

I'd be very interested if you have any thoughts on whether this would
be difficult for us to implement, and if not, what the best way to go
about it would be? Any advice would be gratefully received.

Best regards,
Mike

[Jesús García Crespo]

Hi Mike,

Thank you for your suggestion. We have been received a similar user report before. I can find up to two related issues in our tracker:

http://code.google.com/p/qubit-toolkit/issues/detail?id=1922

http://code.google.com/p/qubit-toolkit/issues/detail?id=1018

On Fri, Feb 24, 2012 at 2:02 AM, Mike B <mike...@gmail.com> wrote:

The way I'd like it to work is that you'd navigate to the relevant
institution using the standard search functionality, and then, on that
institution's details page, choose "Add Holding" or whatever.  This
would lead to a new ISAD(G) form with the repository information pre-
filled.

It's a good option but I am afraid that makes the workflow too complicated. I am not an archivist though. I also can't picture how would you manage a big list of holdings, could you explain that?

 

I'd be very interested if you have any thoughts on whether this would
be difficult for us to implement, and if not, what the best way to go
about it would be?  Any advice would be gratefully received.

It would be great to find a solution that we can merge in ICA-AtoM and include in our future release. As you know, we are open to contributors and there is a wiki page giving some details about it: http://qubit-toolkit.org/wiki/index.php?title=Development

Whatever you end up doing, we can help with the tech support. I just would like to design a solution that fit with all the requirements if possible.

Regards,

--
Jesús García Crespo,
Software Engineer, Artefactual Systems Inc.
http://www.artefactual.com | +1.604.527.2056

[Mike B]

Hi Jesús,

Thanks for your reply. Unless there are some issues I haven't yet
discovered, I think I've worked out a simple way to do this. Here's
what I've done:

- Added a new link at the bottom of the Isdiah indexSuccess template
pointing to: ;add/isad?repository=<Repo-Slug>

- Added the following lines in the Isad editAction controller's
earlyExecute method:

if (isset($this->request->repository))
{
$params = $this->context->routing->parse(Qubit::pathInfo($this-
>request->repository));
$this->resource->repository = $params['_sf_route']->resource;
}

The repository is then pre-filled in the resulting form and the people
entering the ISAD(G) data won't have to touch it. I expect there's a
better, more robust, way to do it, but I think this will work for now.

Thanks,
Mike

On Feb 25, 1:58 am, Jesús García Crespo <je...@artefactual.com> wrote:
> Hi Mike,
>
> Thank you for your suggestion. We have been received a similar user report
> before. I can find up to two related issues in our tracker:
>

> http://code.google.com/p/qubit-toolkit/issues/detail?id=1922http://code.google.com/p/qubit-toolkit/issues/detail?id=1018