buda-base / buda-demo-data

Manual data built for the beta demo

Vagrant scripts for BUDA platform instanciation

The base platform is built using Vagrant and VirtualBox:

1. Install Vagrant and VirtualBox.
2. Download or git clone this repository.
3. cd into the unzipped directory or git clone
4. install VirtualBox guest additions with vagrant plugin install vagrant-vbguest
5. run vagrant up to summon a local instance

Or for an AWS EC2 instance:

1. install the vbguest plugin: vagrant plugin install vagrant-vbguest
2. and run the command: vagrant up or rename Vagrantfile.aws to Vagrantfile and run vagrant up --provider=aws

This will grind awhile installing all the dependencies of the BUDA platform.

Once the initial install has completed the command: vagrant ssh will connect to the instance where development, customization of the environment and so on can be performed as for any headless server.

Similarly, the jena-fuseki server will be listening on:

http://localhost:13180/fuseki

Lds-pdi application is accessible at :

http://localhost:13280/

(see https://github.com/buda-base/lds-pdi/blob/master/README.md for details about using this rest services)

The command: vagrant halt will shut the instance down. After halting (or suspending the instance) a further: vagrant up will simply boot the instance without further downloads, and vagrant destroy will completely remove the instance.

If running an AWS instance, after provisioning access the instance via ssh -p 15345 and delete Port 22 from /etc/ssh/sshd_config and sudo systemctl restart sshd. This will further secure the instance from attacks on port 22.

buda-demo-data's Issues

copyright on Wenli

see http://iiifpres.bdrc.io/2.1.1/collection/wio:bdr:WSBB_WKG

failure at io.bdrc.budademodata.Upload.main(Upload.java:116)

When buda2:~/bin/db-load runs as part of the nightly migration, the following is occurring. I've changed the scripts so that failure in demo data is just a warning and otherwise ignored:

[INFO] --- exec-maven-plugin:1.6.0:java (default-cli) @ budademodata ---
transfer files to http://buda1.bdrc.io:13180/fuseki/newcorerw
add src/main/resources/files/loc.ttl
add src/main/resources/files/cbcat_annotation.ttl
add src/main/resources/files/ederge.ttl
add src/main/resources/files/wenli.ttl
add src/main/resources/files/bca.ttl
add src/main/resources/files/mns.ttl
add src/main/resources/files/shantideva.ttl
didn't find graph http://purl.bdrc.io/graph/tmpbudademodata
[WARNING] 
org.apache.jena.atlas.web.HttpException: 403 - Forbidden
	at org.apache.jena.riot.web.HttpOp.exec(HttpOp.java:1091)
	at org.apache.jena.riot.web.HttpOp.execHttpPut(HttpOp.java:972)
	at org.apache.jena.rdfconnection.RDFConnectionRemote.lambda$doPutPost$4(RDFConnectionRemote.java:399)
	at org.apache.jena.rdfconnection.RDFConnectionRemote.exec(RDFConnectionRemote.java:560)
	at org.apache.jena.rdfconnection.RDFConnectionRemote.doPutPost(RDFConnectionRemote.java:396)
	at org.apache.jena.rdfconnection.RDFConnectionRemote.put(RDFConnectionRemote.java:343)
	at io.bdrc.budademodata.Upload.main(Upload.java:116)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.codehaus.mojo.exec.ExecJavaMojo$1.run(ExecJavaMojo.java:282)
	at java.lang.Thread.run(Thread.java:748)
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------

sets of targets

For annotations with multiple targets / bodies, the set could be qualified as described here