10min

Development progress update

Owen Stephens

15min

eUsage App - future development plans

Stefan Dombek

35minImplementers' topic: URL validation

URLs in Agreements and LIcenses documents

Owen Stephens

With the Q release, the validation of URL fields in Agreements and Licenses has changed. The URLs to wikis and Jiras, which only resolve internally, are no longer validated. Same happens to file paths. As a result, libraries can no longer save the records where they have entered respective information in the URL field.

Wish: add another field for URLs that don’t fit the validation criteria.

Alternative: allow flexibility in validation

Example values from ZBW that we’re storing in our agreements and licenses. We’re not neccessarily keen to add all of those data into the URL field. With Quesnelia, the only appropriate field is labled “Physical description” what seems a bit odd. Maybe this field could be renamed to support all kinds of “non urls”.

• Agreements supplementary documents > Physical location:

  • URL that only resolves internally: http://zbwintern/jira/browse/LM-2616

• Licenses core documents > Physical location:

  • File path of PDF file, e.g. contract document:

    • As path with server name: \\server\zbwshare\040_PB_A\ERM\E-Medien-Verwaltung\Produkte\Einzelsubskriptionen\AGBs\AIS\2021-06-30_EBSCO_Aussage_dauerhafter_Zugriff.pdf

    • As Windows path: G:\040_PB_A\ERM\E-Medien-Verwaltung\Produkte\Einzelsubskriptionen\AGBs\AIS\2021-10-13_EBSCO_Aussage_dauerhafter_Zugriff_ und_Fernleihbedingungen.pdf

  • File path to Outlook message: "G:\040_PB_A\ERM\E-Medien-Verwaltung\Produkte\Einzelsubskriptionen\AGBs\CognizantKeine Fernleihe.msg"