Resolver code update - Thursday 22 October 2020

[ni...@lansley.com]

Hello, my fellow Resolver Community Edition fans!

This message is just a heads up that I am planning a code update on Thursday 22 October which:

1. Improves the performance of MS SQL database access by the Data Entry API / UI service, especially useful if you are using a cloud-based MS SQL service (such as SQL Azure) rather than a dedicated server.
2. Bug fixes and code improvements, mainly for the Data Entry API.
3. Several improvements to the Data Entry API's data responses thanks to your feedback. Our API is now more API-standards compliant with a 'count' and 'data' properties. If you have connected your application(s) to the API directly, then you may find they need to be altered to read response data from the 'data' property of the returned JSON rather than directly from JSON root. If you use the UI, the JavaScript in the upload and download pages have already been adjusted.
4. Security vulnerabilities brought up to date (so, eliminated!)

Apart from the API's slightly altered output, All other changes are backwards compatible - your existing MS SQL and Mongo databases will work with existing data unchanged since the last version.

You may have noticed that we have taken advantage of Github's excellent 'Deoendabot' security assessment service and that it is has highlighted some outdated dependencies. This is a side-effect of only updating Resolver CE's repository every three months. As long as you use 'npm install' on each application that makes up Resolver on a fairly regular basis (monthly is ideal), then you will find security vulnerabilities auto-squashed by the latest versions of dependent libraries.

The updated container images will also be available on Docker Hub on Thursday, so all you need to do is 'git pull' the repo as normal, then 'kubectl apply -k .\' for your Kubernetes cluster to update to the latest code without missing a beat. If you have your own Kubernetes YAML files, just look inside the files in the /k8s folder of the repo, and change the version number of the container image URL in your files to match the repo's versions.

RESOLVE to stay safe out there, and look forward to Thursday!

Best regards

Nick Lansley

[Andrea Volpini]

Hi Nick, 

I am new to the community and I apologize in advance if my request has been addressed already but, I would like to build a demo for one of our E-Commerce clients, using the Resolver and I can upload the required product data but I am currently missing: the authentication key and a sample file (template) that we can use to upload the data.

I am representing WordLift: we build Product Knowledge Graphs using the schema.org vocabulary and the linked data stack to improve SEO.

Many thanks for your help and congratulations for the latest update! Can't really wait to test it!   

[ni...@lansley.com]

Hi Andrea

First of all, welcome!

No worries, always good to ask! Here are some points to help you.

1. If you have followed the guide at https://github.com/gs1/GS1_DigitalLink_Resolver_CE (Readme.MD) then hopefully you have a working SQL database with example data inside.
2. If so, use the authentication key of 13 '5's - '5555555555555' - to upload your data.
3. You can add and update (and delete) more accounts using the Python program accounts.py in 'Python Admin Clients'. If you are running Resolver CE on your local computer (for example, in Docker Engine) then it will work straightaway. If you have installed Resolver CE at some other IP address or domain name then you will need to edit accounts.py to change the name. It's at the very top of the file so easy to spot.
4. You will see example spreAasheet and example CSV format files to use for uploading in the folder 'Example Files to Upload'. Use these as the basis for your own data.

If you get stuck on any of these points let me know and we can schedule a call.

Good luck and have a great weekend

Cheers

Nick