Re: [Archivesspace_Users_Group] Related Agents link strangeness

[Bowers, Kate A.]

I think it is really searching:
University OR of OR Denver

Try keying in  University AND Denver and see if you have better luck.

(Annoying default OR operator is annoying.)

Kate

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Kevin Clair
Sent: Tuesday, January 02, 2018 4:52 PM
To: Archivesspace Users Group (archivesspace_users_group@lyralists.lyrasis.org) 

Subject: [Archivesspace_Users_Group] Related Agents link strangeness

Hello,

We've noticed some peculiar behavior when adding Related Agent links to 
Corporate Entity records in ArchivesSpace. When typing the name of the Agent we 
wish to link in the Related Agents form, the typeahead drop-down list populates 
with unrelated terms. For example, if we were to try and enter a University of 
Denver constituent unit as the later form of a name for a different DU 
corporate entity, typing "university of denver" into the text field brings up a 
drop-down list of mostly Family records. This only happens when the search 
string contains spaces; searches on a single word bring up more or less the 
results we would expect.

Two screenshots are attached: one with the results when "university" is the 
search, and one with the results when "university of denver" is the search (the 
drop-down results are the same whether or not the period is included).

Has anyone else noticed anything like this?

thanks!  -k

___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Processing notes

[Jordon Steele]

Christie,

Like Kevin, we use this note to communicate administrative information that 
doesn’t need to be published but ought to be conveyed to staff, especially if 
it’s information that doesn’t neatly align with a specific note that could be 
unpublished. For example, I used it to explain to staff why we decided to 
change the identifier of a collection from one normally reserved for manuscript 
collections to one that we use for university records collections. The idea is 
that having information like this in the Repository Processing Note ensures 
that it’s more likely to be seen by staff than having it buried in, say, a more 
specific note that’s marked “unpublished.”

Best,

Jordon

Jordon Steele
Hodson Curator of the University Archives
Special Collections
The Sheridan Libraries
Johns Hopkins University
3400 N Charles St
Baltimore, MD 21218
410-516-5493
jste...@jhu.edu

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Kevin Clair
Sent: Tuesday, January 02, 2018 4:34 PM
To: Archivesspace Users Group 
Subject: Re: [Archivesspace_Users_Group] Processing notes

Hi Christie,

At the University of Denver we use it in both Resource and Archival Object 
records as a note to other archivists indicating processing or cataloging tasks 
that were left unfinished for one reason or another, or other administrative 
things that we don’t want published in the PUI. The idea is that if the actions 
listed in the Repository Processing Note get taken, we remove the text that’s 
there.

We have a report that pulls the information from that field for review that we 
run periodically when setting processing priorities: 
https://github.com/duspeccoll/archivesspace_reports/tree/master/resources/resource_processing_notes_report

-k

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 [mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Christie Peterson
Sent: Tuesday, January 02, 2018 2:28 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Processing notes

Hello,

Can anyone on this list speak to what was intended to go in the "Repository 
Processing Note" text field for Resources, which the tooltip tells me does not 
appear in any exports or reports?

Can anyone give me a use case for why they populate this field in addition to 
(or instead of?) an unpublished "Processing Information" note?

Thanks,

Christie Peterson
--
❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️
Christie S. Peterson
Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeter...@smith.edu

pronouns: she/her/hers
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Processing notes

[Kevin Clair]

Three main reasons, in descending order of importance:


1.   At the top of the record so easy to see at a glance

2.   Easier to query in a report

3.   More ephemeral, so less inclined to go to the trouble of navigating 
subforms to enter that information

-k

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Christie Peterson
Sent: Tuesday, January 02, 2018 2:37 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Processing notes

Thanks for the quick response, Kevin. Is there any particular reason why you 
use that note field, instead of the Collection Management subrecord, for that 
purpose?

Christie

On Tue, Jan 2, 2018 at 4:34 PM Kevin Clair 
mailto:kevin.cl...@du.edu>> wrote:
Hi Christie,

At the University of Denver we use it in both Resource and Archival Object 
records as a note to other archivists indicating processing or cataloging tasks 
that were left unfinished for one reason or another, or other administrative 
things that we don’t want published in the PUI. The idea is that if the actions 
listed in the Repository Processing Note get taken, we remove the text that’s 
there.

We have a report that pulls the information from that field for review that we 
run periodically when setting processing priorities: 
https://github.com/duspeccoll/archivesspace_reports/tree/master/resources/resource_processing_notes_report

-k

From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org
 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org]
 On Behalf Of Christie Peterson
Sent: Tuesday, January 02, 2018 2:28 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Processing notes

Hello,

Can anyone on this list speak to what was intended to go in the "Repository 
Processing Note" text field for Resources, which the tooltip tells me does not 
appear in any exports or reports?

Can anyone give me a use case for why they populate this field in addition to 
(or instead of?) an unpublished "Processing Information" note?

Thanks,

Christie Peterson
--
❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️
Christie S. Peterson
Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeter...@smith.edu

pronouns: she/her/hers
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
--
❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️
Christie S. Peterson
Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeter...@smith.edu

pronouns: she/her/hers
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Processing notes

[Christie Peterson]

Thanks for the quick response, Kevin. Is there any particular reason why
you use that note field, instead of the Collection Management subrecord,
for that purpose?

Christie

On Tue, Jan 2, 2018 at 4:34 PM Kevin Clair  wrote:

> Hi Christie,
>
>
>
> At the University of Denver we use it in both Resource and Archival Object
> records as a note to other archivists indicating processing or cataloging
> tasks that were left unfinished for one reason or another, or other
> administrative things that we don’t want published in the PUI. The idea is
> that if the actions listed in the Repository Processing Note get taken, we
> remove the text that’s there.
>
>
>
> We have a report that pulls the information from that field for review
> that we run periodically when setting processing priorities:
> https://github.com/duspeccoll/archivesspace_reports/tree/master/resources/resource_processing_notes_report
>
>
>
> -k
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:
> archivesspace_users_group-boun...@lyralists.lyrasis.org] *On Behalf Of 
> *Christie
> Peterson
> *Sent:* Tuesday, January 02, 2018 2:28 PM
> *To:* Archivesspace Users Group
> *Subject:* [Archivesspace_Users_Group] Processing notes
>
>
>
> Hello,
>
>
>
> Can anyone on this list speak to what was intended to go in the
> "Repository Processing Note" text field for Resources, which the tooltip
> tells me does not appear in any exports or reports?
>
>
>
> Can anyone give me a use case for why they populate this field in addition
> to (or instead of?) an unpublished "Processing Information" note?
>
>
>
> Thanks,
>
>
>
> Christie Peterson
>
> --
>
> ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️
>
> Christie S. Peterson
>
> Head of Technical Services for Special Collections
>
> Smith College
>
> Northampton, Mass.
>
> 413-585-2996 <(413)%20585-2996>
>
> cpeter...@smith.edu
>
>
>
> pronouns: she/her/hers
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
-- 
❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️
Christie S. Peterson
Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeter...@smith.edu

pronouns: she/her/hers
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Processing notes

[Kevin Clair]

Hi Christie,

At the University of Denver we use it in both Resource and Archival Object 
records as a note to other archivists indicating processing or cataloging tasks 
that were left unfinished for one reason or another, or other administrative 
things that we don’t want published in the PUI. The idea is that if the actions 
listed in the Repository Processing Note get taken, we remove the text that’s 
there.

We have a report that pulls the information from that field for review that we 
run periodically when setting processing priorities: 
https://github.com/duspeccoll/archivesspace_reports/tree/master/resources/resource_processing_notes_report

-k

From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Christie Peterson
Sent: Tuesday, January 02, 2018 2:28 PM
To: Archivesspace Users Group
Subject: [Archivesspace_Users_Group] Processing notes

Hello,

Can anyone on this list speak to what was intended to go in the "Repository 
Processing Note" text field for Resources, which the tooltip tells me does not 
appear in any exports or reports?

Can anyone give me a use case for why they populate this field in addition to 
(or instead of?) an unpublished "Processing Information" note?

Thanks,

Christie Peterson
--
❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️
Christie S. Peterson
Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeter...@smith.edu

pronouns: she/her/hers
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Processing notes

[Christie Peterson]

Hello,

Can anyone on this list speak to what was intended to go in the "Repository
Processing Note" text field for Resources, which the tooltip tells me does
not appear in any exports or reports?

Can anyone give me a use case for why they populate this field in addition
to (or instead of?) an unpublished "Processing Information" note?

Thanks,

Christie Peterson
-- 
❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️ ❄️
Christie S. Peterson
Head of Technical Services for Special Collections
Smith College
Northampton, Mass.
413-585-2996
cpeter...@smith.edu

pronouns: she/her/hers
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Error when saving records in 2.2.2

[Trevor Thornton]

Thanks, Mark. I don't *think* any of the plugins we're using touch that
part of the view, but it could be doing something similar in another
include. I'll check it out.

On Tue, Jan 2, 2018 at 1:35 PM, Custer, Mark  wrote:

> Hi, Trevor:
>
>
>
> I don’t think that we’ve seen this particular issue, but we did have
> another issue when upgrading from 1.5.x to 2.x which I’ll mention here in
> case it’s of any use in your circumstance.  For us, the issue was simply a
> plugin.  In our case, whenever we saved a record after upgrading, the user
> was forced to re-load the page in order for the entire page to refresh
> correctly so that the user could get on with their work.  The problem was
> that the plugin overrode some new code in the 2.x version of the
> application, specifically the Enable Reorder Mode button that’s now part of
> the Edit mode, which resulted in a javascript error whenever a new archival
> object was added.  Once we updated the plugin to be 2.x compliant, though,
> everything behaved as expected again with the plugin turned on.
>
>
>
> Do you have any plugins in your instance that could be causing this
> issue?  Just based on that experience, I’d want to rule out that
> possibility first.
>
>
>
> Mark
>
>
>
>
>
>
>
> *From:* archivesspace_users_group-boun...@lyralists.lyrasis.org [mailto:
> archivesspace_users_group-boun...@lyralists.lyrasis.org] *On Behalf Of *Trevor
> Thornton
> *Sent:* Tuesday, 02 January, 2018 11:49 AM
> *To:* Archivesspace 
> *Subject:* [Archivesspace_Users_Group] Error when saving records in 2.2.2
>
>
>
> Hi everybody-
>
>
>
> Since we updated to 2.2.2 we have had an inconsistently recurring issue
> when creating and editing records. When the user saves the record they are
> immediately given an error message indicating that the record did not save
> (sometimes the message is "Failed to save your changes", sometimes it's
> "Record not found"). But upon refreshing the page it turns out that the
> changes actually did save, and there are no errors logged on the backend,
> which makes me think it's just a frontend issue. This has happened so far
> with resource, archival object, subject and agent records.
>
>
>
> It doesn't happen every time, which is kind of good, but it makes it
> impossible to reliably reproduce the problem - the same set of actions that
> triggered the error once will not necessarily trigger it a second time.
> This makes it hard to diagnose what's going on or to report the issue in a
> helpful way.
>
>
>
> Has anyone else noticed anything like this?
>
>
>
> -Trevor
>
>
>
> --
>
> Trevor Thornton
>
> Applications Developer, Digital Library Initiatives
>
> North Carolina State University Libraries
>
> ___
> Archivesspace_Users_Group mailing list
> Archivesspace_Users_Group@lyralists.lyrasis.org
> http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group
>
>


-- 
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Re: [Archivesspace_Users_Group] Error when saving records in 2.2.2

[Custer, Mark]

Hi, Trevor:

I don’t think that we’ve seen this particular issue, but we did have another 
issue when upgrading from 1.5.x to 2.x which I’ll mention here in case it’s of 
any use in your circumstance.  For us, the issue was simply a plugin.  In our 
case, whenever we saved a record after upgrading, the user was forced to 
re-load the page in order for the entire page to refresh correctly so that the 
user could get on with their work.  The problem was that the plugin overrode 
some new code in the 2.x version of the application, specifically the Enable 
Reorder Mode button that’s now part of the Edit mode, which resulted in a 
javascript error whenever a new archival object was added.  Once we updated the 
plugin to be 2.x compliant, though, everything behaved as expected again with 
the plugin turned on.

Do you have any plugins in your instance that could be causing this issue?  
Just based on that experience, I’d want to rule out that possibility first.

Mark



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
[mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org] On Behalf Of 
Trevor Thornton
Sent: Tuesday, 02 January, 2018 11:49 AM
To: Archivesspace 
Subject: [Archivesspace_Users_Group] Error when saving records in 2.2.2

Hi everybody-

Since we updated to 2.2.2 we have had an inconsistently recurring issue when 
creating and editing records. When the user saves the record they are 
immediately given an error message indicating that the record did not save 
(sometimes the message is "Failed to save your changes", sometimes it's "Record 
not found"). But upon refreshing the page it turns out that the changes 
actually did save, and there are no errors logged on the backend, which makes 
me think it's just a frontend issue. This has happened so far with resource, 
archival object, subject and agent records.

It doesn't happen every time, which is kind of good, but it makes it impossible 
to reliably reproduce the problem - the same set of actions that triggered the 
error once will not necessarily trigger it a second time. This makes it hard to 
diagnose what's going on or to report the issue in a helpful way.

Has anyone else noticed anything like this?

-Trevor

--
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

[Archivesspace_Users_Group] Error when saving records in 2.2.2

[Trevor Thornton]

Hi everybody-

Since we updated to 2.2.2 we have had an inconsistently recurring issue
when creating and editing records. When the user saves the record they are
immediately given an error message indicating that the record did not save
(sometimes the message is "Failed to save your changes", sometimes it's
"Record not found"). But upon refreshing the page it turns out that the
changes actually did save, and there are no errors logged on the backend,
which makes me think it's just a frontend issue. This has happened so far
with resource, archival object, subject and agent records.

It doesn't happen every time, which is kind of good, but it makes it
impossible to reliably reproduce the problem - the same set of actions that
triggered the error once will not necessarily trigger it a second time.
This makes it hard to diagnose what's going on or to report the issue in a
helpful way.

Has anyone else noticed anything like this?

-Trevor

-- 
Trevor Thornton
Applications Developer, Digital Library Initiatives
North Carolina State University Libraries
___
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group