[Archivesspace_Users_Group] publish feature

[Brad Westbrook]

Hi, Sarah,

I am glad to hear Haverford is moving along with its implementation of ArchivesSpace.

I’ve interpolated some brief responses to your questions below.

Cheers,

Brad W.

From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Sarah Horowitz
Sent: Thursday, July 07, 2016 3:33 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] publish feature

Hello everyone,
We're new to ArchivesSpace, and I have what may be some basic questions.

1.       Is it possible to set "publish" as a default for just one type of thing? That is, we want all our resources to be public, but not our accessions. Is there a way to set that as the default?
One can set “publish” to have the default value = “true” (all new records in all cases are immediately published) or “false” (all new records are not immediately published).  The default is for all records where the publish option occurs.  It cannot presently be constrained to a specific type of record.  That, however, would be a good feature, for which I have filed a feature request:  https://archivesspace.atlassian.net/browse/AR-1525.

2.      Does the publish check box cascade? That is, if I check publish at the resource level, do I also have to check it in that record for every single note?
No, the publish button does not cascade.  It applies to the record or record area in which it appears.  The resource and digital object records have an option “Publish All” which appears across the top of the parent record template:
[cid:image001.png at 01D1D92D.EDB23550]

Clicking on that will mark all occurrences of  “Publish” in the resource or digital object record tree as “true”.


3.      I set up default values in the resource record while logged in as myself, a systems admin. However, when other people are logged into the repository, they do not see these defaults. I thought that these defaults were supposed to apply to the whole repository? (That is what we want them to do.)

Is the preference for “Pre-populate records” in the Global Preferences and Repository Preferences set to true?

Is there any chance they are looking for the resource default values in the resource component records?

You might have to provide more details about what is happening.


4.      How can I change the "browse" display to show more than the default 10 per page?
The setting for the how many items are listed per page is in the “config.rb” file located in the application stack at C:\[path]\archivesspace-v1.4.2\archivesspace\config.
The setting appears near the top of the file and has a default of “10”.  You can increase that to a larger number.  When you do, be sure to remove the hash mark at the start of the line.  Also be sure to use a text editor like Wordpad or Notepad to edit the file.
[cid:image002.png at 01D1D92E.D6052740]
This modified setting will list 60 items per page.
You may not have access to the config.rb, in which case you will need to request your IT staff to make the change.  The change will be true for all organizations using the ArchivesSpace instance.



Many thanks for your assistance.
Sarah

--
Sarah Horowitz
Curator of Rare Books and Manuscripts
Head of Quaker & Special Collections
Haverford College Libraries
Haverford College
370 Lancaster Ave.
Haverford, PA 19041
(610) 896-2948
shorowitz at haverford.edu<mailto:shorowitz at haverford.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160708/bc1786c9/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 11989 bytes
Desc: image001.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160708/bc1786c9/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image002.png
Type: image/png
Size: 17374 bytes
Desc: image002.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20160708/bc1786c9/attachment-0001.png>