Hi Aman,
For a manual installation you'll also need to install the public gateway application that the public browser connects to. The README in that project should have the instructions you need, but let us know if you have any problems: https://github.com/collectionspace/cspace-public-gateway
Once you have the gateway working, you can configure the gatewayUrl in the WordPress plugin to point to it.
For the script location, you can use the latest version published to npm, which is 1.3.2. This would be accessible via CDN at https://unpkg.com/cspace-public-browser@1.3.2/dist/cspacePublicBrowser.min.js, or https://cdn.jsdelivr.net/npm/cspace-public-browser@1.3.2/dist/cspacePublicBrowser.min.js (your choice).
Thanks,
Ray
From: Amandeep Kapila amandeep.kapila@gmail.com
Sent: Monday, January 9, 2023 5:55 PM
To: Ray Lee
Subject: Re: [Talk] CollectionSpace Public Browser
Hello,
Thanks for responding back. My CollectionSpace version is 7.0. No, not the automated installer, I installed it manually, on debian 11.
On Sat, Jan 7, 2023 at 5:07 AM Ray Lee <ray.lee@lyrasis.orgmailto:ray.lee@lyrasis.org> wrote:
Hi Aman,
What version of CollectionSpace are you using? Did you install it using the automated installer?
Thanks,
Ray
From: Amandeep Kapila <amandeep.kapila@gmail.commailto:amandeep.kapila@gmail.com>
Sent: Thursday, December 29, 2022 11:48 AM
To: Talk@lists.collectionspace.orgmailto:Talk@lists.collectionspace.org
Subject: [Talk] CollectionSpace Public Browser
Dear all,
I have an instance of Collection Space running at CollectionSpace (punlib.infohttp://punlib.info)http://punlib.info:8180/cspace/core/login and want to make my collection available through Public Browser, using my Wordpress instance on the same server. From the documentation at GitHub - collectionspace/wp-collectionspace: WordPress plugin for CollectionSpacehttps://github.com/collectionspace/wp-collectionspace, I installed the collectionspace plugin in my wordpress instance but I am facing difficulties in configuring it. I have also created the required gateway user.
Further, the documentation says,
Set custom fields to configure the browser. There are two custom fields. Both are required:
script location: The URL to the CollectionSpace browser JavaScript application, e.g. https://unpkg.com/cspace-public-browser@1.2.0/dist/cspacePublicBrowser.min.js. Your CollectionSpace administrator should be able to provide the correct value for your CollectionSpace installation.
config: Configuration settings for the CollectionSpace browser application, in JavaScript object notation (not restricted to JSON). At a minimum, specify the basename and gatewayUrl settings. basename should be set to "/collection/" followed by the slug of the page (the last element of the permalink). gatewayUrl should be set the the URL of your CollectionSpace public gateway server. Your CollectionSpace administrator should be able to provide the correct value. For example, if your page slug is core, your config might look like:
{
basename: '/collection/core',
gatewayUrl: 'https://core.dev.collectionspace.org/gateway/core',
}
I can't figure out the values that I should replace for my url. I have tried many permutations but no success.
Can someone elaborate on how I should figure out the right settings for my server?
Regards,
Aman
Hi Aman,
For a manual installation you'll also need to install the public gateway application that the public browser connects to. The README in that project should have the instructions you need, but let us know if you have any problems: https://github.com/collectionspace/cspace-public-gateway
Once you have the gateway working, you can configure the gatewayUrl in the WordPress plugin to point to it.
For the script location, you can use the latest version published to npm, which is 1.3.2. This would be accessible via CDN at https://unpkg.com/cspace-public-browser@1.3.2/dist/cspacePublicBrowser.min.js, or https://cdn.jsdelivr.net/npm/cspace-public-browser@1.3.2/dist/cspacePublicBrowser.min.js (your choice).
Thanks,
Ray
________________________________________
From: Amandeep Kapila <amandeep.kapila@gmail.com>
Sent: Monday, January 9, 2023 5:55 PM
To: Ray Lee
Subject: Re: [Talk] CollectionSpace Public Browser
Hello,
Thanks for responding back. My CollectionSpace version is 7.0. No, not the automated installer, I installed it manually, on debian 11.
On Sat, Jan 7, 2023 at 5:07 AM Ray Lee <ray.lee@lyrasis.org<mailto:ray.lee@lyrasis.org>> wrote:
Hi Aman,
What version of CollectionSpace are you using? Did you install it using the automated installer?
Thanks,
Ray
________________________________________
From: Amandeep Kapila <amandeep.kapila@gmail.com<mailto:amandeep.kapila@gmail.com>>
Sent: Thursday, December 29, 2022 11:48 AM
To: Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org>
Subject: [Talk] CollectionSpace Public Browser
Dear all,
I have an instance of Collection Space running at CollectionSpace (punlib.info<http://punlib.info>)<http://punlib.info:8180/cspace/core/login> and want to make my collection available through Public Browser, using my Wordpress instance on the same server. From the documentation at GitHub - collectionspace/wp-collectionspace: WordPress plugin for CollectionSpace<https://github.com/collectionspace/wp-collectionspace>, I installed the collectionspace plugin in my wordpress instance but I am facing difficulties in configuring it. I have also created the required gateway user.
Further, the documentation says,
****************************************************************************************
Set custom fields to configure the browser. There are two custom fields. Both are required:
script location: The URL to the CollectionSpace browser JavaScript application, e.g. https://unpkg.com/cspace-public-browser@1.2.0/dist/cspacePublicBrowser.min.js. Your CollectionSpace administrator should be able to provide the correct value for your CollectionSpace installation.
config: Configuration settings for the CollectionSpace browser application, in JavaScript object notation (not restricted to JSON). At a minimum, specify the basename and gatewayUrl settings. basename should be set to "/collection/" followed by the slug of the page (the last element of the permalink). gatewayUrl should be set the the URL of your CollectionSpace public gateway server. Your CollectionSpace administrator should be able to provide the correct value. For example, if your page slug is core, your config might look like:
{
basename: '/collection/core',
gatewayUrl: 'https://core.dev.collectionspace.org/gateway/core',
}
******************************************************************************************
I can't figure out the values that I should replace for my url. I have tried many permutations but no success.
Can someone elaborate on how I should figure out the right settings for my server?
Regards,
Aman