Skip to content

Split off configuration always unique to an archive #77

Description

@drn05r

In cfg/cfg.d/z_orcid_support_advance.pl there is several bits of configuration which will always need to be updated differently for each EPrints archive. It would make sense to split these off into a separate configuration file, maybe called zz_orcid_support_advance_credentials_affiliation.pl

$c->{orcid_support_advance}->{client_id} = "XXXX";
$c->{orcid_support_advance}->{client_secret} = "YYYY";

#Details of the organization for affiliation inclusion - the easiest way to obtain the RINGGOLD id is to add it to your ORCID user record manually, then pull the orcid-profile via the API and the identifier will be on the record returned.
$c->{"plugins"}->{"Event::OrcidSync"}->{"params"}->{"affiliation"} = {
    "organization" => {
        "name" => "My University Name", #name of organization - REQUIRED
        "address" => {
            "city" => "My Town",  # name of the town / city for the organization - REQUIRED if address included
            "region" => "Countyshire",  # region e.g. county / state / province - OPTIONAL
            "country" => "GB",  # 2 letter country code - AU, GB, IE, NZ, US, etc. - REQUIRED if address included
        },
        "disambiguated-organization" => {
            "disambiguated-organization-identifier" => "ZZZZ",  # replace ZZZZ with Institutional identifier from the recognised source
            "disambiguation-source" => "GRID", # Source for institutional identifier should be GRID or RINGGOLD (see https://www.grid.ac/institutes for GRID's free lookup service)
        }
    }
};

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions