[Archivesspace_Users_Group] component trees not appearing in public view of AS

[Brad Westbrook]

Hi, Julia,

Is it possible that the components are not marked to be published?

[cid:image004.png at 01D11590.3D781990][cid:image005.jpg at 01D11590.3D781990]


If not, you can A) indicate each component  in the tree you want to publish to the public interface or B) select the "Publish All" option on the parent record, which will publish everything in the description.


[cid:image004.png at 01D11590.3D781990][cid:image006.jpg at 01D11590.3D781990]

Let us know if that does work.

Cheers,

Brad W.

Bradley D. Westbrook
Program Manager
brad.westbrook at lyrasis.org<mailto:brad at archivesspace.org>
800.999.8558 x2910
678.235.2910
bradley_d_westbrook (Skype)
[cid:image003.png at 01CE734E.FD759D30]





From: archivesspace_users_group-bounces at lyralists.lyrasis.org [mailto:archivesspace_users_group-bounces at lyralists.lyrasis.org] On Behalf Of Novakovic, Julia
Sent: Monday, November 02, 2015 1:20 PM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] component trees not appearing in public view of AS

Hello,

My institution had about 50 full resource records in Archivists' Toolkit which mapped/migrated perfectly over to ArchivesSpace earlier this year. However, I'm having an issue with the resources I've hand-entered into AS since then; the component trees appear fine in the internal side, but in the public view, there is just a three-bar churning  icon there. Does anyone have any advice on what needs to happen so that all of our resources' components appear in the public view? [Screenshots comparing the two (public-side view) attached.] There is nothing else missing from the internal side to the public side for the newly hand-entered records, and I have tried clicking "Publish All" to no avail.

Related: Keyword searching in the internal side works perfectly for discovery of these hand-entered records. When I go to the public view, though, I will get the same search results, but when I click on any of those file records, I get the error message "We're sorry, but something went wrong." Does this mean something isn't linking correctly? I'd appreciate any advice that I can pass along to our Director of IT to fix the problem.

Thanks!
--Julia


Julia Novakovic
Archivist
Associate Editor, American Journal of Play
The Strong
One Manhattan Square
Rochester, NY 14607 U.S.A.
Tel 585-410-6307
Fax 585-423-1886
jnovakovic at museumofplay.org<mailto:jnovakovic at museumofplay.org>
www.museumofplay.org<http://www.museumofplay.org/>

The Strong is home to:
International Center for the History of Electronic Games | National Toy Hall of Fame | World Video Game Hall of Fame
Brian Sutton-Smith Library and Archives of Play | Woodbury School | American Journal of Play

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151102/f92837fd/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image004.png
Type: image/png
Size: 1137 bytes
Desc: image004.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151102/f92837fd/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image005.jpg
Type: image/jpeg
Size: 13275 bytes
Desc: image005.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151102/f92837fd/attachment.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image006.jpg
Type: image/jpeg
Size: 11388 bytes
Desc: image006.jpg
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151102/f92837fd/attachment-0001.jpg>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image007.png
Type: image/png
Size: 7640 bytes
Desc: image007.png
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20151102/f92837fd/attachment-0001.png>