Revision 8269
Added by ben leinfelder about 11 years ago
| docs/user/metacat/source/submitting.rst | ||
|---|---|---|
| 115 | 115 |
install Template |
| 116 | 116 |
install URI |
| 117 | 117 |
install MSERGEANT/XML-LibXSLT-1.58.tar.gz |
| 118 |
install Captcha:reCAPTCHA |
|
| 118 | 119 |
|
| 119 | 120 |
2. Install the required system libraries using Ubuntu/Debian (instructions |
| 120 | 121 |
Red Hat in sidebar) |
| ... | ... | |
| 134 | 135 |
|
| 135 | 136 |
sudo cpan -i Config::Properties |
| 136 | 137 |
sudo cpan -i Scalar::Util |
| 138 |
sudo cpan -i Captcha:reCAPTCHA |
|
| 137 | 139 |
|
| 138 | 140 |
|
| 139 | 141 |
3. Double-check that Metacat's temporary folder, application.tempDir, is |
| ... | ... | |
| 190 | 192 |
corresponding to the "Station Name" and "NCEAS Project" drop-down lists in |
| 191 | 193 |
the registry form, have been removed. |
| 192 | 194 |
|
| 195 |
LDAP account management |
|
| 196 |
~~~~~~~~~~~~~~~~~~~~~~~~ |
|
| 197 |
If you intend to use Metacat's built-in LDAP account management feature, |
|
| 198 |
you will need public and private keys for the reCaptcha widget. |
|
| 199 |
|
|
| 200 |
1. Get private and public recaptcha keys from Google using your Google account: |
|
| 201 |
https://www.google.com/recaptcha/admin/create |
|
| 202 |
|
|
| 203 |
2. Configure Metacat to use those keys in the metacat.properties file: |
|
| 204 |
|
|
| 205 |
:: |
|
| 206 |
|
|
| 207 |
ldap.recaptcha.publickey=<your public key> |
|
| 208 |
ldap.recaptcha.privatekey=<your private key> |
|
| 209 |
|
|
| 210 |
3. Restart Tomcat |
|
| 211 |
|
|
| 212 |
|
|
| 193 | 213 |
Using HTML Forms (the HTTP Interface) |
| 194 | 214 |
------------------------------------- |
| 195 | 215 |
Metacat's HTTP interface supports Get and Post requests and a variety of actions (Table 4.1) that facilitate information retrieval and storage. HTTP requests can be sent from any client application that communicates using the Web's HTTP protocol. |
Also available in: Unified diff
include reCaptcha instructions, albeit briefly. https://projects.ecoinformatics.org/ecoinfo/issues/6096