[NEOS Discovery] [Spike] Investigate on Sam's Cataloguing Tool Work

[weiweishi]

Is your feature request related to a problem? Please describe. The original spec is at https://github.com/ualbertalib/NEOSDiscovery/issues/205

And as we identify this is likely not a long-term solution, it is deemed as a high priority issue for us to get to the code freeze for NEOS Discovery. The final solution will depends on:

• ops' team's estimation on setting on the infrastructure on a stand alone instance of NEOS Discovery (in docker)
• any additional development work is required (beyond Sam's initial PR).

The proposed spike is to investigate, if Sam's code change will be able to meet the basic requirements of the tool:

1. pull down catalogue record via catkey through Z39.50
2. allow users to view the record in NEOS Discovery Record View

[pgwillia]

I'm finding that my notes from my previous review hold up https://github.com/ualbertalib/discovery/pull/1180

Need to:

• [x] install yaz in docker container
• [x] initialize a File.join(Rails.root, 'tmp', 'records') for the temporary marc records to live
• [x] fix the redirect_to path

[pgwillia]

Took a look at using ruby's TempFile for this instead but decided it was too much work for the timebox. http://vaidehijoshi.github.io/blog/2015/10/06/fleeting-filing-with-ruby-tempfile/

[pgwillia]

Pushed the branch https://github.com/ualbertalib/discovery/tree/cataloguing_tool.

• Building with docker build . -t ualbertalib/discovery:cataloguing
• docker-compose up -d
• visit localhost:3002/cataloguing

[pgwillia]

Dockerhub configured to build the cataloguing_tool branch and tag it as 'cataloguing'.

To deploy on an environment with docker and docker-compose installed, you do not need to clone the git repository. Only two files are needed.

wget https://raw.githubusercontent.com/ualbertalib/discovery/cataloguing_tool/docker-compose.yml
wget -O .env_deployment https://raw.githubusercontent.com/ualbertalib/discovery/cataloguing_tool/.env_deployment_sample
# edit this file to have sane values
docker-compose up -d

[pgwillia]

Regarding this bullet in the issue description

ops' team's estimation on setting on the infrastructure on a stand alone instance of NEOS Discovery (in docker)

The cataloguing tool was built in Discovery (that's where the ingest code lives). A stand alone instance of NEOS Discovery won't be particularly useful.

Furthermore there is a Dockerfile in NEOS Discovery, but I've found that it contains errors.

...
Step 8/10 : RUN bundle install
 ---> Running in b7de2e8d557b
Warning: the running version of Bundler (1.15.4) is older than the version that created the lockfile (1.16.2). We suggest you upgrade to the latest versio
n of Bundler by running `gem install bundler`.
Fetching gem metadata from https://rubygems.org/............
Fetching version metadata from https://rubygems.org/...
Fetching dependency metadata from https://rubygems.org/..
Fetching https://github.com/upenn-libraries/blacklight-ris.git
Your bundle is locked to logger (1.2.8), but that version could not be found in
any of the sources listed in your Gemfile. If you haven't changed sources, that
means the author of logger (1.2.8) has removed it. You'll need to update your
bundle to a different version of logger (1.2.8) that hasn't been removed in
order to install.
The command '/bin/sh -c bundle install' returned a non-zero code: 7

[weiweishi]

@pgwillia The request is to allow NEOS libraries to view the records in the NEOS Discovery record view. If we have this on the Discovery instance, do we have to get the NEOS Discovery record view into this instance of the cataloguing tool? Does it fair to say that the fastest route forward would be a UAT like environment with cataloguing_tool branch in a docker and let the NEOS libraries to access it?

[pgwillia]

Here's how Sam's work appears:

1. Visit /cataloguing
2. Clicking 'Submit' will
   • pull the marc record from ualapp.library.ualberta.ca the Unicorn z39.50 server
   • change the catkey by adding the 'tmp' prefix
   • use rake solr:marc:index to add the document to the Solr index
3. Then you are redirected to the catalog record view for that item

When resources have been provisioned with appropriate access what you see above is ready to go.

Second requirement is to "allow users to view the record in NEOS Discovery Record View" which hasn't been satisfied yet. Here's some ideas about how this could be satisfied

• port indexing code to branch in NEOSDiscovery
• port catalog record display to branch in Discovery
• have both applications dockerized and running in parallel
  • maybe nginx could be configured to serve cataloguing from discovery and the rest from NEOS discovery?