<div dir="ltr">Thank you for the reminder about this functionality, Kevin. Unfortunately, it doesn't seem to be working as expected with v.3.0.2 -- even though I have checked the Publish checkbox for the default Global, Repository, <i>and</i> User preferences, newly created agent records still default to unpublished. I've confirmed this to be the case not only with our local 3.0.2 instance, but also the community sandbox on this version. The upshot is that I've checked the program testing instance with the upcoming release and this functionality is back to working as expected. All of which is to say, it looks like this issue can be addressed with native functionality in a future release and doesn't warrant a bug report, but I do want to flag it for any folks who might be on 3.0.2.<div><br></div><div>Thanks again!</div><div>Rachel</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Aug 20, 2021 at 9:38 AM Kevin W. Schlottmann <<a href="mailto:kws2126@columbia.edu">kws2126@columbia.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hi Rachel,<div><br></div><div>Re 1), the default publish status, which applies to all record types, can be set at global, repository, and user levels in Preferences. A couple of years ago we set the repository default to true because we would often forget to set newly created agents to publish=true, resulting in published description missing creators and subjects. I just checked our setting, and it was set back to the default (publish=false), so I wonder if this is reset to default when AS is upgraded. We rarely use publish=false for any record type, so a default of publish=true works for us, but that may not be the case for different setups, especially those using the PUI. There was a JIRA request to allow more fine-grained control of publish status for different record types, but it wasn't fleshed out and dev-pri marked it as "Will not do" <a href="https://urldefense.proofpoint.com/v2/url?u=https-3A__archivesspace.atlassian.net_browse_ANW-2D505&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=uGL5GgxToCyQ6zPTB3HHd4kk0SyzlokG4I9GA2FDpgU&s=IDipIDTHNf5oH2yxLqIHUcOZCnpaxZKDdlfk-yoec80&e=" target="_blank">https://archivesspace.atlassian.net/browse/ANW-505</a> </div><div><br></div><div>Re 2), we are seeing similar behavior for shared top containers as well; we are on version 2.8.1. I'd be happy to add our examples to a ticket, as this is annoying and potentially confusing behavior.</div><div><br></div><div>Kevin</div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 19, 2021 at 11:47 AM Rachel Aileen Searcy <<a href="mailto:rachel.searcy@nyu.edu" target="_blank">rachel.searcy@nyu.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">Hello list!<div><br></div><div>We are in the process of upgrading to v.3.0.2, and noticed a few unusual details that I'm hoping to get some more information about. Neither would be deal-breakers to upgrading, but I'm curious if these are intended or perhaps bugs. We first noticed these in our local development instance, but I've been able to replicate them in the community sandbox.</div><div><br></div><div>When I create a new agent record -- either on its own via "Create -- Agent" or within the context of an accession or resource record, the "Publish" checkbox defaults to false. This is new behavior to us, and I'm curious if this is intended (and if so, if there is a way to locally alter this so that new agents default to Publish=True)?<br clear="all"><div><br></div><div>We also saw some potentially buggy behavior with the "sticky" parameters when browsing for containers. For example, when starting from a resource record and browsing for a container, Manage Top Containers pre-populates the interface with my resource record so that only containers linked to it are listed:</div><div><br></div><div><img src="cid:ii_ksj3f5t43" alt="Screen Shot 2021-08-19 at 11.42.55 AM.png" width="542" height="236"><br></div><div><br></div><div>If I want to browse for a shared box, for example, I want to clear the resource field and instead do a container search with a keyword (this screenshot shows my edits to the parameters before selecting "Search"): </div><div><br></div><div><img src="cid:ii_ksj3bbku0" alt="Screen Shot 2021-08-19 at 11.39.48 AM.png" width="542" height="173"><br></div><div>But as soon as I select "Search" my original resource record is re-inserted into the parameters although it doesn't actually seem to be impacting the search results:</div><div><br></div><div><img src="cid:ii_ksj3cyc52" alt="Screen Shot 2021-08-19 at 11.41.14 AM.png" width="542" height="220"></div><div><br></div><div>I'd be happy to put together a JIRA ticket for either of these issues, but first wanted to see if others had insight before doing so.</div><div><br></div><div>Thanks so much. Take care,</div><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Rachel Searcy<br>Accessioning Archivist, Archival Collections Management<br><div><span style="font-size:12.8px">New York University Libraries</span><br></div><div><a value="+12129982631">212.998.2539</a> | <a href="mailto:rachel.searcy@nyu.edu" target="_blank">rachel.searcy@nyu.edu</a> <br></div></div><div>My pronouns are she/her/hers</div></div></div></div></div></div></div></div></div></div></div></div></div>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwMFaQ&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=uGL5GgxToCyQ6zPTB3HHd4kk0SyzlokG4I9GA2FDpgU&s=nnoiQcvkOTUw-zeVG4-ZBe0sVt4lHQsjbSDMEPf1txw&e=" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group</a><br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr">Kevin Schlottmann<br>Head of Archives Processing<br>Rare Book & Manuscript Library<br>Butler Library, Room 801<br><div>Columbia University</div><div><i>Pronouns: he/him/his</i><br></div>535 W. 114th St., New York, NY 10027<br>(212) 854-8483</div></div>
_______________________________________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org" target="_blank">Archivesspace_Users_Group@lyralists.lyrasis.org</a><br>
<a href="https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=uGL5GgxToCyQ6zPTB3HHd4kk0SyzlokG4I9GA2FDpgU&s=nnoiQcvkOTUw-zeVG4-ZBe0sVt4lHQsjbSDMEPf1txw&e=" rel="noreferrer" target="_blank">https://urldefense.proofpoint.com/v2/url?u=http-3A__lyralists.lyrasis.org_mailman_listinfo_archivesspace-5Fusers-5Fgroup&d=DwICAg&c=slrrB7dE8n7gBJbeO0g-IQ&r=WwSkYr7X9POdZNK4180yTjrK5hSljcuCPIN--y1VRZk&m=uGL5GgxToCyQ6zPTB3HHd4kk0SyzlokG4I9GA2FDpgU&s=nnoiQcvkOTUw-zeVG4-ZBe0sVt4lHQsjbSDMEPf1txw&e=</a> <br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div>Rachel Searcy<br>Accessioning Archivist, Archival Collections Management<br><div><span style="font-size:12.8px">New York University Libraries</span><br></div><div><a value="+12129982631">212.998.2539</a> | <a href="mailto:rachel.searcy@nyu.edu" target="_blank">rachel.searcy@nyu.edu</a> <br></div></div><div>My pronouns are she/her/hers</div></div></div></div></div></div></div></div></div></div></div>