buda-base / buda-issues

Use this repository to raise BUDA-wide project issues such as new feature requests, architectural issues and so on

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-issues's Issues

images not displaying for W1NLM503

Images are not displaying for newly synced works like bdr:W1NLM503 and bdr:W1NLM465. They show appropriately on tbrc.org:W1NLM503 and so on.

The ttl looks correct. In particular bdr:V1NLM503_I1NLM503_001 has a proper image list.

I bounced all servers and tried the URLs on several different browsers on two different systems.

Other than the images, bdr:W1NLM503 and so on display as expected.

ability to upload trig files on Fuseki

IIRC, there are bugs when uploading trig files to Fuseki, that's why we convert them into ttl and infer the graph from the file name. For future purposes, we might need to decorelate the graph name from the file (for instance having multiple graphs in one file, or having other file names for some reason). We should report that bug to Jena, Chris can you do that?

editing, updating, and report needs

I'm raising this issue so that the development team can begin collecting information from the library staff regarding features, improvements, and so on regarding the development of dashboard, editor, and features similar to the admin tabs on the current website (when you click on your logged in name in the upper right of the web page).

The Editing Buda document lays out some broad considerations for editing, updating and reporting.

We will be retiring the current standalone DLMS Editor snd moving to a completely browser-based editor which should make deploying updates and other maintenance activities much more productive for all of us.

As you have requests for improvements over the current DLMS Editor or new features including reports and batch updating like reassigning topics, persons and places, please add a reply to this issue.

Thank you

API to access some s3 files

the dimensions.json (sitting on s3 in the same directory as the images) file should be publicly accessible for each volume on a url. I'm a bit hesitant as to what the best URL scheme is... here are a few ideas for the file corresponding to bdr:V4CZ5369_I1KG9223:

• http://purl.bdrc.io/resource/V4CZ5369_I1KG9223/dimensions.json
• http://presentation.bdrc.io/s3files/v:V4CZ5369_I1KG9223/dimensions.json

Note that with the new s3 file (perhaps images.jsonld?) will be read / write on a similar URL so the service / url should be wisely chosen. In both cases I'll probably write most of the code.

@xristy @MarcAgate what do you think the best place would be for that?