You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 6, 2023. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+10-10Lines changed: 10 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
-
# DOECode Web Application
1
+
# DOE CODE Web Application
2
2
3
-
Consists of the "back-end" services and JAX/RS API calls for DOE Code, to be
3
+
Consists of the "back-end" services and JAX/RS API calls for DOE CODE, to be
4
4
accessed by the front-end or presentation layer. This application is targeted
5
5
at a non-EE Java container such as Tomcat, using JPA and JAX/RS (Jersey implementation)
6
6
for persistence layer and web API implementation.
@@ -109,7 +109,7 @@ to obtain the output in YAML format.
109
109
110
110
`POST /services/metadata`
111
111
112
-
Store a given metadata JSON to the DOECode persistence layer in an incomplete or
112
+
Store a given metadata JSON to the DOE CODE persistence layer in an incomplete or
113
113
pending status. The resulting JSON information is returned as the JSON object "metadata",
114
114
including the generated unique IDs as appropriate if the operation was successful. Record
115
115
is placed in the "Saved" work flow.
@@ -121,16 +121,16 @@ format. Does not persist any data.
121
121
122
122
`POST /services/metadata/publish`
123
123
124
-
Store the metadata information to the DOECode persistence layer with a "Published"
124
+
Store the metadata information to the DOE CODE persistence layer with a "Published"
125
125
work flow. JSON is returned as with the "Saved" service above, and this record
126
-
is marked as available to the DOECode search output services. If DataCite information
126
+
is marked as available to the DOE CODE search output services. If DataCite information
127
127
has been configured, this step will attempt to register any DOI entered and update
128
128
metadata information with DataCite.
129
129
130
130
`POST /services/metadata/submit`
131
131
132
132
Post the metadata to OSTI, attempt to register a DOI if possible, and persist
133
-
the information on DOECode. If workflow validations pass, the JSON will be returned
133
+
the information on DOE CODE. If workflow validations pass, the JSON will be returned
134
134
with appropriate unique identifier information and DOI values posted in the
135
135
JSON object "metadata". Data is placed in "Published" state.
136
136
@@ -191,11 +191,11 @@ It is often useful to have a simple database for testing that is not your instit
191
191
3) In Eclipse, open the "Database Development" perspective.
192
192
4) Follow the [Eclipse Documentation](http://help.eclipse.org/kepler/index.jsp?topic=%2Forg.eclipse.datatools.common.doc.user%2Fdoc%2Fhtml%2Fasc1229700387729.html) to create a Derby Connector, create a connection profile, and connect to Derby.
193
193
194
-
In step 4, be sure to select "Derby Client Driver" instead of "Derby Embedded Driver." DOE Code is not currently configured to work with the Embedded driver.
194
+
In step 4, be sure to select "Derby Client Driver" instead of "Derby Embedded Driver." DOE CODE is not currently configured to work with the Embedded driver.
195
195
196
196
## Running on AWS
197
197
198
-
The DOE Code server works well on AWS. For the default RHEL 7 instance, the server can be executed with a Derby database for storing using the following rough steps:
198
+
The DOE CODE server works well on AWS. For the default RHEL 7 instance, the server can be executed with a Derby database for storing using the following rough steps:
199
199
1) Create the instance. Make sure your security group is configured to let the necessary ports through (normally 8080).
200
200
2) SSH into the instance using your key. Issue the following commands to download and install prerequisites including Java, Git, and Derby.
201
201
```bash
@@ -250,7 +250,7 @@ cd ~/server
250
250
## SOLR for Searching and Indexing (Dissemination)
251
251
252
252
If configured in the deployment profile, Apache SOLR may be used for an indexing and
253
-
searching service for DOECode. Setting up SOLR distribution package version 6.6.0
253
+
searching service for DOE CODE. Setting up SOLR distribution package version 6.6.0
254
254
as a stand-alone service as follows:
255
255
256
256
1) Download the [SOLR package from Apache](http://http://lucene.apache.org/solr/)
0 commit comments