Motivation:

A bug was introduced with commit aee25f9f where OAI-PMH URLs without a
trailing slash have one added; for example, the Identify request
targeting PSI changes from `https://doi.psi.ch/oaipmh/oai?verb=Identify`
to `https://doi.psi.ch/oaipmh/oai/?verb=Identify`.

For some endpoints, this distinction is important, resulting in the
requests failing.

Modification:

Fix regression so that the correct URL is used.

Result:

The PSI endpoint is now shown (correctly) to be working.

Motivation:

Some OAI-PMH endpoints are broken; moreover, they're broken in such a
way that makes harvesting information wastes a lot of time without
producing useful information.

The specific example is the ISIS endpoint, which is both very slow (~10
seconds per request) and, after ~9 hours of havesting returns a
resumptionToken that results in failures in a subsequent ListIdentifiers
request.

The ESS endpoint is also broken.  While also annoying, the impact is
less because of special handling when a server hasn't provided useful
information.

The goal is to allow selective disabiling of harvesting while continuing
to update high-level OAI-PMH information based on the Identity call.

Modification:

Add a `skip-harvesting` boolean option.  If set with the value true then
harvesting is skipped for this endpoint.

Result:

It's possible to update all endpoints without a very long and fruitless
time spent harvesting from broken endpoints.

Motivation:

The current OAI-PMH information is recorded as `datasets`.  However,
this assumes that the items underlying the harvested OAI-PMH records
correspond to datasets.  This is not guaranteed, and there are
counter-examples.

OAI-PMH describes three concepts: resource, item and record.  The
OAI-PMH responses provide records (descriptive metadata of some item) or
identifiers thereof.  However, since OAI-PMH requires repositories to
support Dublin Core records, it seems a reasonable assumption for there
to be a 1:1 relationship between each Dublin Core record and some
corresponding item.

Therefore, we can use the metadata-agnostic `item` concept when
describing the information about the endpoint.

Modification:

Update script to record information under `items` node in the facilities
YAML file.

Update the Jekyll to consume this information when rendering the
corresponding HTML.

Result:

No observable change, but the facilities YAML file now uses the more
neutral 'items' instead of 'datasets'.

Motivation:

OAI-PMH provides admin contact details as email addresses. This could
prove useful information.  One such situation is when the OAI-PMH
endpoint is not working.  When this happens, the admin contact details
are no longer available from the endpoint, so caching the values would
prove useful.

Modification:

Update code to capture the admin contact information and record it
against the facility-specific information.

If, when updating the OAI-PMH details, the admin contact details are
discovered (from the OAI-PMH endpoint) then any existing contact details
are replaced with the discovered information; otherwise, any existing
admin contact details are left unmodified.

Result:

We collect and cache OAI-PMH admin contact details in the facility
metadata.

The `check_search_api.rb` script contained a bug because of the
following issue:

    https://github.com/panosc-eu/search-api/issues/75

This updates the script and rectifies the status of institutes.

The AMBCAT contract is now signed.  Add link to OSCARS web-page
fix corruption in JSON.

Unfortunately, Darren has left MAX-IV and is no longer involved with
LEAPS.

Mark SIG as "active".

Add mandate (from Andy)

Update SIG information with information from kick-off meeting.
  * Add mandate.
  * Switch status to 'Active'.

Closes #24

This partly resolves issue #14.

Antonio Fernández Maltas authored 5 months ago and Paul Millar committed 5 months ago

- /_data/members.yml
- /_data/facilities.yml
- /assets/images/profile-pic-om.png