Hi Kim,
I was just wondering if there was any chance the webinar might be recorded and
distributed so international users who aren’t able to attend can get some
further information on the program?
I’m in Melbourne (AEST), and I know there are a couple of other Australian
institutions using
Hello Everyone,
Please forgive any misunderstandings on my part, as I'm relatively new to this
software and the project.
I'm currently working with an installation of ArchivesSpace which has been
updated to 2.5.0, and I've encountered a problem in which Event "Outcome"
values can be persisted
We require everyone to have LDAP credentials (volunteers too) to log in and use
any systems. If for some reason that couldn't work, I'd have the volunteer
work in Excel or other txt file format. We have workflows to import data from
CSV or spreadsheet templates. That covers most cases!
I believe that if you use LDAP for authentication it can still fall back to
the standard database authentication (where you set the user's password
within ArchivesSpace). The 'admin' user is authenticated this way.
On Tue, Sep 25, 2018 at 12:34 PM Tang, Lydia wrote:
> Hi Nancy,
> Thanks for
Hi Nancy,
Thanks for your feedback! Ed Busch added your idea into the JIRA ticket.
https://archivesspace.atlassian.net/browse/ANW-534 Keeping the username
static makes a lot of sense.
On a tangential note, for people who are using LDAP, how do you handle people
who aren’t affiliated with
Lydia, all -
ANW-534 could introduce challenges for our users and workflows. We use LDAP,
and would want to prevent users from modifying usernames or passwords in the
archivesspace UI.
Could user account editing be configurable, to accommodate LDAP workflows?
For example, perhaps this could
Hi Everyone,
We've just updated from 1.5.1 to 2.3.2. In this new version, we no longer have
extent calculating capability. Is there a separate plug-in for this function?
Thanks,
Miranda
Miranda Mims
Special Collections Archivist for Discovery & Access
Department of Rare Books, Special
I can confirm that we're seeing this behavior also (version 2.5). It happens
for corporate bodies used as a subject or as a creator:
Subject:
Kansas
Federation of Women's Clubs,
