Update datatig.yaml: access_publicDatabase should be type URL

[jarofgreen]

No description provided.

[jarofgreen]

The JSON Schema says it's a URL.

However, some records have multiple values with a , and some in a way that it would be hard to separate them into individual URLs automatically eg ca-cc, NO-BRC, ie-cro, mw-nbm

Some records have strings eg et-mfa, ID-KDN , ID-PRO , je-oac, several ke-,

Should we commit to this field being a single URL, and fix the above, or something else?

(Asking as I was trying to put a big "search data" button on new list page, and I found it wasn't clear I could do that)

[emmajclegg]

@jarofgreen - yes, I've noticed as well that some lists have multiple urls in this field.

I'd vote in favour of us committing to a single url in access_publicDatabase. It is so important from a usability perspective that people can find the searchable online database (if there is one), so your "search button" sounds great to me.

Detail on other online search pages, descriptives, etc. can be put in one of the other free text fields like access_onlineAccessDetails.

So - if we can easily identify the lists affected by invalid/multiple urls in this field, I'm happy to prioritise them as ones to review next.

[kd-ods]

@jarofgreen - I think the action for us here (not for you this week!) is:

• Identify the lists affected by invalid/multiple urls in this field (using the bulk org-id record data from here)
• Fix the access_publicDatabase field value in the identified lists (to make each a single, valid URL)
• Merge this PR

That right? (cc @emmajclegg )

[jarofgreen]

@kd-ods Yes.

You could also merge this now, and then do the work to fix things up. That way there would be help for people editing new/existing records sooner, and hopefully stop more bad data being created.

Linking to DataTig/DataTig#47 - work on that would help here.