Setting up a new staging location (v4.1.4)

33 views
Skip to first unread message

Rachel Trent

unread,
Mar 6, 2014, 2:13:48 PM3/6/14
to curators-wor...@googlegroups.com
We are excited to start testing Curator's Workbench, however we've run into a snag setting up our basic preferences. We aren't able to add any new staging locations. We've tried URIs to the local file system and to a networked file server, experimenting with various syntax but not running into any luck. The error we continue to receive is "Cannot load config file from [file:/s:/test, or whichever path attempted]."

Could we be missing a configuration file that we should have placed in the intended staging area?

Thanks,

Rachel Trent
State Library of North Carolina

Gregory Jansen

unread,
Mar 11, 2014, 10:41:02 AM3/11/14
to curators-wor...@googlegroups.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hi Rachel,
I was glad to hear that our state library is looking at the workbench. Yes, the staging location configuration is tricky. It doesn't have a UI that allows one to configure locations locally, aside from the default <project>/data location. Other locations are generally shared across an organization, so what we do is put a configuration file on the web.

For the CDR example, see this one:
https://cdr.lib.unc.edu/static/stages.json

That file defines a set of staging locations, giving names (URIs) to folders on shared drives. The names are used to reference staged files in the METS manifest, since different computers may see the same drive as a different letter or local path, for example Macs and PCs use different paths.

The format is JSON. Here is an example with just one mapping

{
"tag:cdr.lib.unc.edu,2013:/cdr_projects/":{
        "name":"CDR Projects",
        "mappings":[
            "file:/Volume/projects/cdr/staging"
        ],
        "confirmFile":"born_digital"
    }
}

The only required elements are the initial URI, starting with "tag:" above, and the name field. The mappings are common paths to that staging space within your organization. (Workbench will try using them to connect to the space) The confirm file can be a folder name or file name within the staging area. It is used to confirm that the workbench has connected to the space, also optional.

I hope this helps. I need to document this. Let me know how it goes.
Greg

On 03/06/2014 02:13 PM, Rachel Trent wrote:
> We are excited to start testing Curator's Workbench, however we've run into a snag setting up our basic preferences. We aren't able to add any new staging locations. We've tried URIs to the local file system and to a networked file server, experimenting with various syntax but not running into any luck. The error we continue to receive is "Cannot load config file from [/file:/s:/test, or whichever path attempted/]."

>
> Could we be missing a configuration file that we should have placed in the intended staging area?
>
> Thanks,
>
> Rachel Trent
> State Library of North Carolina
>
> --
> You received this message because you are subscribed to the Google Groups "Curator's Workbench Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to curators-workbench...@googlegroups.com <mailto:curators-workbench...@googlegroups.com>.
> For more options, visit https://groups.google.com/groups/opt_out.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBCgAGBQJTHyB+AAoJEKXVBfOA+6qCfg4QAJO8yA45KyuhVwQE/3psIZKs
4EoJTiME7czgkkExQfGOuuP9N/g3mFFvuZFZon9bTX/u4i43Z2ohGkLZfVT9HuRg
efo2Jn8NNpFDqky/6R08Ivl1LVIWR+m1lmNmRPZ77FrRbsJP33Ym3CASACKR298/
9qVJ5Ph5+5yVYv2KoMI/BPwzCrJk8BvBNsjwyRwdQ+ZV8XhPtzJN5JP4RhSJTX88
Puo9qDdU+Cqq1X7ikLI8Bc70HY5vODF7LE6UQFL4DUOeqkst7pk9M36wDnH94MyD
XCguMDsqzQYGWpEhY9ADXK6GjrEBDfCMOq2sOlfGhh/09WOzFfbRQzzIfW07Yqzp
6TtTMDf51PcE97fg6meZdP7BEaD2qsagYQ2VbcvZkCdYI4Prue+7AvIPNjWc/RWi
392lADZSrilVvyk0ZqfwgEEksRjLhJ/5fWGOBDZO/Wn7PN2WXwogLcKVTIQfzGrG
+tTGFVwyipxSflESNaguR4Q+OO6nQ5vA7TDoCb8geRAzXog9zEfvivLCoCYPU3um
7ietZL99G9f83XjUk9DwSr+IoY1aGHsIRw9o+SUKd7rnVpYQwBHWAVEMC8UvWbOm
o/BVwMtMEbFBRVOf3ubS7R7chsQ6SBMKKbY0DPtRor0Bjp/VMTWUuA/bzOHSxcm5
pAy2XObLU48oWQuL+TO3
=/k8K
-----END PGP SIGNATURE-----

Reply all
Reply to author
Forward
0 new messages