Skip to content

Tim Hutchinson

← Atlas Systems

My feedback

1 result found

  1. Import location information from a file without staff mediation

    15 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    4 comments  ·  Aeon Ideas » Staff Client  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Tim Hutchinson commented  · 

    I'm coming at this from the perspective of an institution considering the deployment of Aeon.

    In our case we would need to initiate a file request based on a search of this database, as opposed to using it to look up location data for an external request. This would be the only way to ensure data consistency in the requests.

    In answer to your questions:
    - everyone who manages the Access database would have access to Aeon
    - it's typically updated a few times a week (mostly with new accessions rather than changes to existing accessions). It's used for both accession records and location tracking - and therefore used to identify relevant collections for reference enquiries, especially collections not described in our public database.
    - A relevant export could live in Aeon. We would want to make sure it was updated in Aeon periodically (at least weekly?), and ideally on an automated schedule rather than needing a manual update. Typically, new accessions wouldn't be needed for retrieval right away.

    Something else to note is that this data should only be accessible to Archives staff, not public users.

Feedback and Knowledge Base

(thinking…)