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
Feature branch was originally started to upgrade the Data Hub Foundation version from 5.1.0 to 5.7.2 but when DH moved 5.8 during the changes, I removed all the DH components entirely. They are brought into the project with hubInit instead which is much more standard operating procedure and much cleaner.
* Add codepoint to match with created Element Range Index definitions.
* DH version bump to 5.7.2
* DH 5.1.0 to 5.7.2
* Gradle version 5.2.1 -> 6.9.1
* Remove DeployHubOtherServersCommand unit test refs
* mlDHFVersion no longer has any impact starting in version 5.3.0. You may safely remove this from your properties file.
* runAllPPM -> examples:person-position-matching:runAll
* Add range-element-index instructions.
* Comment out unit test framework.
* Remove instruction re: data zip file which longer exists nor is necessary
* runAll -> runAndDeployAll
* Close bracket for cleanliness
* Formatting, HADOOP_HOME, and remove Windows drug load instruction.
* Fix -input_file_path for drugZipLoad. Clarify instructions.
* Update loadPubMedCentral instructions to include FTP site and path location.
* Adjust -input_file_path of pubMedInputFlowFTP. loadStudy -> LoadStudy
* loadDrug -> LoadDrug flow-name change.
* Internal grove-core-react-redux-containers replaced with public github accessible version.
* Deleted all of the DH hubInit generated files.
* Update versions, repos, and remove DH compile.
* Changed the instructions to initialize Data Hub with hubInit. Formatting.
* Remove deprecated jcenter.
* Configure example specific indexes using mlConfigPaths instead of modifying final-database.json directly.
Copy file name to clipboardExpand all lines: README.md
+17-10Lines changed: 17 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,6 @@ There are two main steps to use this application:
11
11
## 1. Install Research Hub
12
12
#### Prerequites
13
13
1. MarkLogic 9.0-11 or 10.0-3
14
-
2. DataHub 5.1.0 (included)
15
14
3. Java 8+ (used for running QuickStart and gradle-wrapper)
16
15
4. Node 10 or 12
17
16
5. Optionally Docker Desktop if you want/need to run MarkLogic inside a container
@@ -22,12 +21,18 @@ It is recommended to use the default ports, DB names, and App Server names defin
22
21
23
22
#### 1.2 Deploy DHF
24
23
25
-
./gradlew mlDeploy
24
+
First, generate Data Hub source files:
25
+
26
+
`./gradlew hubInit`
27
+
28
+
Second, deploy the database components (including Data Hub) to MarkLogic:
29
+
30
+
`./gradlew mlDeploy`
26
31
27
32
### 1.3 Install UI
28
33
29
-
cd ui
30
-
npm install
34
+
`cd ui`
35
+
`npm install`
31
36
32
37
## 2. Install One of the Included Examples
33
38
Two examples are included in this code base. By copying these example files into the main code area, and modifying some core files, you will be installing a fully-functional Research Hub. These are included to provide sample code and patterns for building your own research hubs.
@@ -42,37 +47,39 @@ To install one of the example domains, follow the README.md file in that example
42
47
You can create your own entity by running a gradle command to scaffold the files you need.
The task will create the necessary files and print out their locations for you to go edit.
70
75
71
76
## Running the UI
72
77
After installing Research Hub and a domain, you can start the ui using:
73
78
74
-
cd ui
75
-
npm start
79
+
`cd ui`
80
+
`npm start`
81
+
82
+
If the start fails, it may be necessary to install the nodemon (Node Monitor), cross-env, and concurrently packages with `npm install nodemon`, `npm install cross-env`, and `npm install concurrently` respectively from the ui directory. Typically, these are installed with `-g` option which makes the packages globally available across all projects.
76
83
77
84
## Running Tests
78
85
After installing Research Hub and a domain, you can run any tests that were created by going to http://localhost:8015/test/ (or http://localhost:8115/test/ if using our Docker setup), and using the UI there to run tests.
This line will include the indexes defined in the `examples\hr360\src\main\ml-config\databases\final-database.json` file to the base version of the final database defined in `src\main\ml-config\databases\final-database.json`.
75
+
76
+
68
77
### Build and deploy the changes
69
78
70
79
Use this commands to deploy all the changes and code to the backend:
0 commit comments