oregondigital / controlledvocabularymanager Goto Github PK

View Code? Open in Web Editor NEW

21.0 20.0 4.0 1.15 MB

Rails application with Blazegraph for managing controlled vocabularies in RDF.

Home Page: http://opaquenamespace.org

License: GNU General Public License v3.0

Ruby 86.07% JavaScript 2.35% HTML 9.78% CoffeeScript 0.22% SCSS 0.64% Dockerfile 0.28% Shell 0.66%

ruby blazegraph rails rdf json-ld linked-data authority-control

controlledvocabularymanager's Introduction

Controlled Vocabulary Manager

Overview

Rails app connected to Blazegraph for managing local controlled vocabularies for Oregon Digital. Currently powering http://OpaqueNamespace.org

Local Development Setup

Requires: Ruby 2.5, Java 8 for Blazegraph

git clone https://github.com/OregonDigital/ControlledVocabularyManager.git
cd ControlledVocabularyManager
bundle install
bundle exec rake triplestore_adapter:blazegraph:reset
bundle exec rake db:create && bundle exec rake db:migrate
bundle exec rake git_dev:create_dev_repo
bundle exec rake sunspot:solr:start

Start the servers:

bundle exec rails server

You can browse the app via http://localhost:3000, and check on the blazegraph server at http://localhost:9999/blazegraph

Create admin user

In order to do anything, you'll need to create a user with admin privileges.

With the application loaded, click the 'Login' link in the top-right. Then click 'Sign up' and fill out the form.

Once the user is created, open a new terminal window and run:

bundle exec rails console
me = User.first
# You should see a User object returned with the name and email you created
me.role = 'admin reviewer editor'
me.save

Now refresh the application in the browser. You should see an Admin Dashboard link in the top-right 'profile' menu to manage users, a Review link in the top navigation, and on the Vocabularies page you should see a button to create a new one.

controlledvocabularymanager's People

Contributors

Stargazers

Watchers

Forkers

collegeoftheholycross scholarworks mindis baitcenter

controlledvocabularymanager's Issues

Display Terms on Vocabulary URI view

Get vocabulary view and form showing all desired properties

But... do we want all properties shown? Just title and publisher? (That's what OD's JSONLD terms use) Is the form going to be using the same properties as the view?

UI for managing vocabularies

UI for adding a term in a vocabulary

Output child terms on Vocab n-triples and JSON-LD

The N-Triples and JSON-LD outputs don't include child terms

Bootstrap UI

Tombstone Vocabularies

e.g. Don't delete but serve some message that says I've been deleted

Github Authentication / Organization Authorization

Clean up existing opaque_ns data

Lots of dates are invalid format
Change 'People' to 'Names' ?
Move data from 'Creator' and 'Publisher' if needed

Creation form is including blank string triples

Editing vocabularies doesn't work

It's using term validations and thus can't find which vocab it's in - since it IS the vocab. We probably need a vocab #edit/#update.

Display list of vocabularies

Paginate child terms

Create new version of Vocabularies

Add capability for multiple attributes

On the edit form, there should be a way to add multiple labels, etc. Although we should probably decide what attributes there can be multiple instances of.

Redirect term to other vocab

Related to #38

Do we use a 301?

Persist AT model to Marmotta.

Hide edit/create links if not logged in

Use buttons for 'Create...' and 'Edit' actions

Use buttons to help emphasize actions vs. navigation links

Auto-Complete for Controlled Types on Ingest Form

flow for logging in

A proper flash message for unauthorized, allow them to see the root page, and make the log in button work

Add created/modified attributes on save

Batch Ingest from JSONLD

Frontend to Grab RDF from remote URLs and assign it a URI

UI for creating a Vocabulary

Sparql Endpoint

Bootstrap Template

Edit Vocabularies

Edit label and comment
update modified date

Use #rdf_subject instead of base_uri+id

Most relevant here: https://github.com/OregonDigital/ControlledVocabularyManager/blob/master/app/views/terms/show.html.erb#L3

Is `repository` being used properly?

I suspect I'm just confused, but looking at things like the TermForm, it allows repository to be, e.g., TermFactory instead of an RDF::Marmotta instance. This makes calls to #exists? very different if you're using a form object vs. what GraphToTerms returns. From the injector, tracing through the stack determines that calling term_form.repository.exists? calls TermFactory, which calls Term, which eventually hits our active triples adapter. But calling term_form.__getobj__.repository.exists? doesn't work, as RDF::Marmotta is the Term object's repository, and it has no exists? method.

Should we be calling exists? on the repository? Or should we make something smarter for existence check that use the Term/Vocabulary class instead?