Set up PURL account for term namespace(s)

[stuartasutton]

On our weekly Monday call, we decided to set up a PURL account to handle redirection for the JDX schemas. This does not involve the URI's of any other resources. Since the PURL service is intended to assist in maintaining persistent access to the schema over time, the account should be held by a someone that will be persistently associated with the JDX.

PURL Service: https://archive.org/services/purl/ PURL Help: https://archive.org/services/purl/help

The PURL "jdx" is available. After you return from creating an Internet Archive account (sends you over to the Internet Archive). you can come back to the PURL service and login. Your screen should then look like this:

You want to create:

Name: /jdx/terms/ Type: partial Target: https://raw.githubusercontent.com/jobdataexchange/Data-Modeling/master/jdxTerms.json

Name:/jdx/terms Type: 302 (Found) Target: http://purl.org/jdx/terms/

After creating the PURLS, you should be able to access the jdxTerms.json file via:

http://purl.org/jdx/terms/ or http://purl.org/jdx/terms

and properties and classes:

http://purl.org/jdx/terms/addressCountry

Stuart P.S. I am no expert at the PURL service

[stuartasutton]

@tplagge, @robinsonkwame:

Any progress on getting the PURL redirects set up?

[robinsonkwame]

I (@robinsonkwame) plan on following up that this Tuesday.

Sent from my iPhone

On Jan 21, 2019, at 9:35 AM, Stuart Sutton notifications@github.com wrote:

@tplagge, @robinsonkwame:

Any progress on getting the PURL redirects set up? EDIT - archive.org seems to be down for maintenance, will check later today; I did set up an internet archive brighthive.io account yesterday — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[robinsonkwame]

note: Internet Archive's PURL domain creation endpoint returns an error when trying to create PURLs, reached out to info@archive.org last week.

EDIT - reached out to an engineer directly (mark@archive.org) on 1/5, no response to date

[stuartasutton]

@robinsonkwame, please try and register the PURL now. I would try, but then I would own it and that's not what's wanted. I contacted my colleagues at Dublin Core and one of the members of their technology infrastructure committee discovered the problem as well a few months back. He notified Internet Archive via email and got no response, but the service to add PURLs was restored. Let me know if it is still not allowing new PURL registrations and I'll follow-up, even if it means going to their office in San Francisco (I drive by it at least once a week).

[robinsonkwame]

Unfortunately the service still doesn't work; I just tried right now from https://archive.org/services/purl/new_domain as soon as I got your comment and received the same error that we've seen previously. I'm afraid we'll need a direct follow-up.

[stuartasutton]

OK, I'll take it from here with communications with Internet Archive. Stay tuned...

On Mon, Feb 18, 2019 at 6:56 AM Kwame Porter Robinson < notifications@github.com> wrote:

Unfortunately the service still doesn't work; I just tried right now from https://archive.org/services/purl/new_domain as soon as I got your comment and received the same error that we've seen previously. I'm afraid we'll need a direct follow-up.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jobdataexchange/Data-Modeling/issues/9#issuecomment-464761828, or mute the thread https://github.com/notifications/unsubscribe-auth/ACzYpqqtqAstgXQiPIuUUc2cUfIv7ofmks5vOr87gaJpZM4YXbPw .

[stuartasutton]

I'll see what I can do first with an email and then a "visit" if necessary.

[stuartasutton]

@robinsonkwame, please try once again to create the JDX PURL. Last week, everyone discovered that their existing PURL's were not resolving. Dublin Core sent their info email an URGENT email. The service is back up. It may have been that that was the original problem, or part of it. So, please try again and let me know.

Stuart

[robinsonkwame]

@stuartasutton I tried again and unfortunately I'm receiving the same error. Specifically, the response is,

Server error
The server encountered an internal error and was unable to complete your request.

Either the server is overloaded or there is an error in the application.

If this error persists please contact us at info@archive.org

This service is an initiative of the Internet Archive, a 501(c)(3) non-profit,building a digital library of Internet sites and other cultural artifacts in digital form.

[robinsonkwame]

Great, was able to create both PURLs, the below should work now (validated against one item)

After creating the PURLS, you should be able to access the jdxTerms.json file via:

http://purl.org/jdx/terms/
or
http://purl.org/jdx/terms

and properties and classes:

http://purl.org/jdx/terms/addressCountry

[robinsonkwame]

note: a class reference, http://purl.org/jdx/terms/Condition, does not work.

[stuartasutton]

Kwame, we need to return to the PURL setup and make the following adjustments:

1. Per the instructions above (https://github.com/jobdataexchange/Data-Modeling/issues/9#issue-379302254), we need to create two PURLs, not one:

Name: /jdx/terms/ Type: partial Target: https://raw.githubusercontent.com/jobdataexchange/Data-Modeling/master/jdxTerms.json

Name:/jdx/terms Type: 302 (Found) Target: http://purl.org/jdx/terms/

We created the first one, but not the second.

2. I (think I) made a mistake in the instructions leading to the partial PURLs like http://purl.org/jdx/terms/Condition not resolving. I think that the problem is that we need the hash (#) anchor appended:

https://raw.githubusercontent.com/jobdataexchange/Data-Modeling/master/jdxTerms.json#

I won't be certain of the second until you edit the PURL adding the hash and we see whether we get resolution. Since testing through the browser won't trigger the right content negotiation, the behaviors of the two purls will appear the same...but will be correct.

[robinsonkwame]

Great, I've made the following changes which hopefully gets us where we need to be:

• Added /jdx/terms 302 type
• Edited /jdx/terms/ to target https://raw.githubusercontent.com/jobdataexchange/Data-Modeling/master/jdxTerms.json#

Let me know if that doesn't fix it.

cheers kwame

On Sat, Jul 13, 2019 at 10:04 AM Stuart Sutton notifications@github.com wrote:

Kwame, we need to return to the PURL setup and make the following adjustments:

1. Per the instructions above (#9 (comment) https://github.com/jobdataexchange/Data-Modeling/issues/9#issue-379302254), we need to create two PURLs, not one:

Name: /jdx/terms/ Type: partial Target: https://raw.githubusercontent.com/jobdataexchange/Data-Modeling/master/jdxTerms.json

Name:/jdx/terms Type: 302 (Found) Target: http://purl.org/jdx/terms/

We created the first one, but not the second.

1. I (think I) made a mistake in the instructions leading to the partial PURLs such that PURLs like http://purl.org/jdx/terms/Condition are not resolving. I think that the problem is that we need the hash (#) anchor appended:

https://raw.githubusercontent.com/jobdataexchange/Data-Modeling/master/jdxTerms.json#

I won't be certain of the second until you edit the PURL adding the hash and we see whether we get resolution. Since testing through the browser won't trigger content negotiation, the behaviors of the two purls will appear the same.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jobdataexchange/Data-Modeling/issues/9?email_source=notifications&email_token=AB5ESR224MXTBJ2W6LJ3KY3P7HOHLA5CNFSM4GC5WPYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3SJAY#issuecomment-511124611, or mute the thread https://github.com/notifications/unsubscribe-auth/AB5ESR5DGQSHAB3ATFANTQ3P7HOHLANCNFSM4GC5WPYA .

[stuartasutton]

Super! Thanks, Kwame.

On Mon, Jul 15, 2019 at 12:15 PM Kwame Porter Robinson < notifications@github.com> wrote:

Great, I've made the following changes which hopefully gets us where we need to be:

• Added /jdx/terms 302 type
• Edited /jdx/terms/ to target

https://raw.githubusercontent.com/jobdataexchange/Data-Modeling/master/jdxTerms.json#

Let me know if that doesn't fix it.

cheers kwame

On Sat, Jul 13, 2019 at 10:04 AM Stuart Sutton notifications@github.com wrote:

Kwame, we need to return to the PURL setup and make the following adjustments:

1. Per the instructions above (#9 (comment) < https://github.com/jobdataexchange/Data-Modeling/issues/9#issue-379302254 ), we need to create two PURLs, not one:

Name: /jdx/terms/ Type: partial Target:

https://raw.githubusercontent.com/jobdataexchange/Data-Modeling/master/jdxTerms.json

Name:/jdx/terms Type: 302 (Found) Target: http://purl.org/jdx/terms/

We created the first one, but not the second.

1. I (think I) made a mistake in the instructions leading to the partial PURLs such that PURLs like http://purl.org/jdx/terms/Condition are not resolving. I think that the problem is that we need the hash (#) anchor appended:

https://raw.githubusercontent.com/jobdataexchange/Data-Modeling/master/jdxTerms.json#

I won't be certain of the second until you edit the PURL adding the hash and we see whether we get resolution. Since testing through the browser won't trigger content negotiation, the behaviors of the two purls will appear the same.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub < https://github.com/jobdataexchange/Data-Modeling/issues/9?email_source=notifications&email_token=AB5ESR224MXTBJ2W6LJ3KY3P7HOHLA5CNFSM4GC5WPYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3SJAY#issuecomment-511124611 , or mute the thread < https://github.com/notifications/unsubscribe-auth/AB5ESR5DGQSHAB3ATFANTQ3P7HOHLANCNFSM4GC5WPYA

.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jobdataexchange/Data-Modeling/issues/9?email_source=notifications&email_token=AAWNRJQAAUWNVBPNQH5PQFTP7TEE3A5CNFSM4GC5WPYKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ6V7XA#issuecomment-511533020, or mute the thread https://github.com/notifications/unsubscribe-auth/AAWNRJWYVZVYIQ6AQBO67T3P7TEE3ANCNFSM4GC5WPYA .