@researchdatabox/raido-openapi-generated-node 0.0.2 → 0.0.3

package/dist/model/models.js

@@ -16,199 +16,85 @@ var __exportStar = (this && this.__exportStar) || function(m, exports) {
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.VoidAuth = exports.OAuth = exports.ApiKeyAuth = exports.HttpBearerAuth = exports.HttpBasicAuth = exports.ObjectSerializer = void 0;
 __exportStar(require("./access"), exports);
-__exportStar(require("./accessBlock"), exports);
 __exportStar(require("./accessStatement"), exports);
 __exportStar(require("./accessType"), exports);
-__exportStar(require("./accessTypeWithSchemaUri"), exports);
 __exportStar(require("./alternateIdentifier"), exports);
-__exportStar(require("./alternateIdentifierBlock"), exports);
 __exportStar(require("./alternateUrl"), exports);
-__exportStar(require("./alternateUrlBlock"), exports);
-__exportStar(require("./apiKey"), exports);
-__exportStar(require("./appUser"), exports);
-__exportStar(require("./appUserExtraV1"), exports);
-__exportStar(require("./authzRequestExtraV1"), exports);
-__exportStar(require("./authzRequestStatus"), exports);
 __exportStar(require("./closedRaid"), exports);
 __exportStar(require("./contributor"), exports);
-__exportStar(require("./contributorBlock"), exports);
-__exportStar(require("./contributorIdentifierSchemeType"), exports);
 __exportStar(require("./contributorPosition"), exports);
-__exportStar(require("./contributorPositionRaidMetadataSchemaType"), exports);
-__exportStar(require("./contributorPositionSchemeType"), exports);
-__exportStar(require("./contributorPositionWithSchemaUri"), exports);
 __exportStar(require("./contributorRole"), exports);
-__exportStar(require("./contributorRoleCreditNisoOrgType"), exports);
-__exportStar(require("./contributorRoleSchemeType"), exports);
-__exportStar(require("./contributorRoleWithSchemaUri"), exports);
-__exportStar(require("./datesBlock"), exports);
 __exportStar(require("./description"), exports);
-__exportStar(require("./descriptionBlock"), exports);
 __exportStar(require("./descriptionType"), exports);
-__exportStar(require("./descriptionTypeWithSchemaUri"), exports);
 __exportStar(require("./failureResponse"), exports);
-__exportStar(require("./generateApiTokenRequest"), exports);
-__exportStar(require("./generateApiTokenResponse"), exports);
 __exportStar(require("./id"), exports);
-__exportStar(require("./idBlock"), exports);
 __exportStar(require("./language"), exports);
-__exportStar(require("./legacyMetadataSchemaV1"), exports);
-__exportStar(require("./migrateLegacyRaidRequest"), exports);
-__exportStar(require("./migrateLegacyRaidRequestMintRequest"), exports);
-__exportStar(require("./mintRaidoSchemaV1Request"), exports);
-__exportStar(require("./mintRaidoSchemaV1RequestMintRequest"), exports);
-__exportStar(require("./mintResponse"), exports);
 __exportStar(require("./modelDate"), exports);
 __exportStar(require("./organisation"), exports);
-__exportStar(require("./organisationBlock"), exports);
-__exportStar(require("./organisationIdentifierSchemeType"), exports);
 __exportStar(require("./organisationRole"), exports);
-__exportStar(require("./organisationRoleSchemeType"), exports);
-__exportStar(require("./organisationRoleType"), exports);
-__exportStar(require("./organisationRoleWithSchemaUri"), exports);
 __exportStar(require("./owner"), exports);
-__exportStar(require("./publicClosedMetadataSchemaV1"), exports);
-__exportStar(require("./publicRaidMetadataSchemaV1"), exports);
-__exportStar(require("./publicReadRaidMetadataResponseV1"), exports);
-__exportStar(require("./publicReadRaidResponseV3"), exports);
-__exportStar(require("./publicServicePoint"), exports);
+__exportStar(require("./raidChange"), exports);
 __exportStar(require("./raidCreateRequest"), exports);
 __exportStar(require("./raidDto"), exports);
-__exportStar(require("./raidListItemV2"), exports);
-__exportStar(require("./raidListItemV3"), exports);
-__exportStar(require("./raidListRequestV2"), exports);
 __exportStar(require("./raidUpdateRequest"), exports);
-__exportStar(require("./raidoMetadataSchemaV1"), exports);
-__exportStar(require("./raidoMetadataSchemaV2"), exports);
-__exportStar(require("./raidoMetaschema"), exports);
-__exportStar(require("./raidoMetaschemaV2"), exports);
-__exportStar(require("./readRaidResponseV2"), exports);
-__exportStar(require("./readRaidV2Request"), exports);
 __exportStar(require("./registrationAgency"), exports);
 __exportStar(require("./relatedObject"), exports);
-__exportStar(require("./relatedObjectBlock"), exports);
 __exportStar(require("./relatedObjectCategory"), exports);
 __exportStar(require("./relatedObjectType"), exports);
 __exportStar(require("./relatedRaid"), exports);
-__exportStar(require("./relatedRaidBlock"), exports);
 __exportStar(require("./relatedRaidType"), exports);
 __exportStar(require("./servicePoint"), exports);
+__exportStar(require("./servicePointCreateRequest"), exports);
+__exportStar(require("./servicePointUpdateRequest"), exports);
 __exportStar(require("./spatialCoverage"), exports);
-__exportStar(require("./spatialCoverageBlock"), exports);
+__exportStar(require("./spatialCoveragePlace"), exports);
 __exportStar(require("./subject"), exports);
-__exportStar(require("./subjectBlock"), exports);
 __exportStar(require("./subjectKeyword"), exports);
 __exportStar(require("./title"), exports);
-__exportStar(require("./titleBlock"), exports);
 __exportStar(require("./titleType"), exports);
-__exportStar(require("./titleTypeWithSchemaUri"), exports);
 __exportStar(require("./traditionalKnowledgeLabel"), exports);
-__exportStar(require("./traditionalKnowledgeLabelBlock"), exports);
-__exportStar(require("./updateAuthzRequest"), exports);
-__exportStar(require("./updateAuthzRequestStatus"), exports);
-__exportStar(require("./updateAuthzResponse"), exports);
-__exportStar(require("./updateRaidoSchemaV1Request"), exports);
-__exportStar(require("./updateRaidoSchemaV2Request"), exports);
 __exportStar(require("./validationFailure"), exports);
 __exportStar(require("./validationFailureResponse"), exports);
-__exportStar(require("./versionResult"), exports);
 const access_1 = require("./access");
-const accessBlock_1 = require("./accessBlock");
 const accessStatement_1 = require("./accessStatement");
 const accessType_1 = require("./accessType");
-const accessTypeWithSchemaUri_1 = require("./accessTypeWithSchemaUri");
 const alternateIdentifier_1 = require("./alternateIdentifier");
-const alternateIdentifierBlock_1 = require("./alternateIdentifierBlock");
 const alternateUrl_1 = require("./alternateUrl");
-const alternateUrlBlock_1 = require("./alternateUrlBlock");
-const apiKey_1 = require("./apiKey");
-const appUser_1 = require("./appUser");
-const appUserExtraV1_1 = require("./appUserExtraV1");
-const authzRequestExtraV1_1 = require("./authzRequestExtraV1");
-const authzRequestStatus_1 = require("./authzRequestStatus");
 const closedRaid_1 = require("./closedRaid");
 const contributor_1 = require("./contributor");
-const contributorBlock_1 = require("./contributorBlock");
-const contributorIdentifierSchemeType_1 = require("./contributorIdentifierSchemeType");
 const contributorPosition_1 = require("./contributorPosition");
-const contributorPositionRaidMetadataSchemaType_1 = require("./contributorPositionRaidMetadataSchemaType");
-const contributorPositionSchemeType_1 = require("./contributorPositionSchemeType");
-const contributorPositionWithSchemaUri_1 = require("./contributorPositionWithSchemaUri");
 const contributorRole_1 = require("./contributorRole");
-const contributorRoleCreditNisoOrgType_1 = require("./contributorRoleCreditNisoOrgType");
-const contributorRoleSchemeType_1 = require("./contributorRoleSchemeType");
-const contributorRoleWithSchemaUri_1 = require("./contributorRoleWithSchemaUri");
-const datesBlock_1 = require("./datesBlock");
 const description_1 = require("./description");
-const descriptionBlock_1 = require("./descriptionBlock");
 const descriptionType_1 = require("./descriptionType");
-const descriptionTypeWithSchemaUri_1 = require("./descriptionTypeWithSchemaUri");
 const failureResponse_1 = require("./failureResponse");
-const generateApiTokenRequest_1 = require("./generateApiTokenRequest");
-const generateApiTokenResponse_1 = require("./generateApiTokenResponse");
 const id_1 = require("./id");
-const idBlock_1 = require("./idBlock");
 const language_1 = require("./language");
-const legacyMetadataSchemaV1_1 = require("./legacyMetadataSchemaV1");
-const migrateLegacyRaidRequest_1 = require("./migrateLegacyRaidRequest");
-const migrateLegacyRaidRequestMintRequest_1 = require("./migrateLegacyRaidRequestMintRequest");
-const mintRaidoSchemaV1Request_1 = require("./mintRaidoSchemaV1Request");
-const mintRaidoSchemaV1RequestMintRequest_1 = require("./mintRaidoSchemaV1RequestMintRequest");
-const mintResponse_1 = require("./mintResponse");
 const modelDate_1 = require("./modelDate");
 const organisation_1 = require("./organisation");
-const organisationBlock_1 = require("./organisationBlock");
-const organisationIdentifierSchemeType_1 = require("./organisationIdentifierSchemeType");
 const organisationRole_1 = require("./organisationRole");
-const organisationRoleSchemeType_1 = require("./organisationRoleSchemeType");
-const organisationRoleType_1 = require("./organisationRoleType");
-const organisationRoleWithSchemaUri_1 = require("./organisationRoleWithSchemaUri");
 const owner_1 = require("./owner");
-const publicClosedMetadataSchemaV1_1 = require("./publicClosedMetadataSchemaV1");
-const publicRaidMetadataSchemaV1_1 = require("./publicRaidMetadataSchemaV1");
-const publicReadRaidMetadataResponseV1_1 = require("./publicReadRaidMetadataResponseV1");
-const publicReadRaidResponseV3_1 = require("./publicReadRaidResponseV3");
-const publicServicePoint_1 = require("./publicServicePoint");
+const raidChange_1 = require("./raidChange");
 const raidCreateRequest_1 = require("./raidCreateRequest");
 const raidDto_1 = require("./raidDto");
-const raidListItemV2_1 = require("./raidListItemV2");
-const raidListItemV3_1 = require("./raidListItemV3");
-const raidListRequestV2_1 = require("./raidListRequestV2");
 const raidUpdateRequest_1 = require("./raidUpdateRequest");
-const raidoMetadataSchemaV1_1 = require("./raidoMetadataSchemaV1");
-const raidoMetadataSchemaV2_1 = require("./raidoMetadataSchemaV2");
-const raidoMetaschema_1 = require("./raidoMetaschema");
-const raidoMetaschemaV2_1 = require("./raidoMetaschemaV2");
-const readRaidResponseV2_1 = require("./readRaidResponseV2");
-const readRaidV2Request_1 = require("./readRaidV2Request");
 const registrationAgency_1 = require("./registrationAgency");
 const relatedObject_1 = require("./relatedObject");
-const relatedObjectBlock_1 = require("./relatedObjectBlock");
 const relatedObjectCategory_1 = require("./relatedObjectCategory");
 const relatedObjectType_1 = require("./relatedObjectType");
 const relatedRaid_1 = require("./relatedRaid");
-const relatedRaidBlock_1 = require("./relatedRaidBlock");
 const relatedRaidType_1 = require("./relatedRaidType");
 const servicePoint_1 = require("./servicePoint");
+const servicePointCreateRequest_1 = require("./servicePointCreateRequest");
+const servicePointUpdateRequest_1 = require("./servicePointUpdateRequest");
 const spatialCoverage_1 = require("./spatialCoverage");
-const spatialCoverageBlock_1 = require("./spatialCoverageBlock");
+const spatialCoveragePlace_1 = require("./spatialCoveragePlace");
 const subject_1 = require("./subject");
-const subjectBlock_1 = require("./subjectBlock");
 const subjectKeyword_1 = require("./subjectKeyword");
 const title_1 = require("./title");
-const titleBlock_1 = require("./titleBlock");
 const titleType_1 = require("./titleType");
-const titleTypeWithSchemaUri_1 = require("./titleTypeWithSchemaUri");
 const traditionalKnowledgeLabel_1 = require("./traditionalKnowledgeLabel");
-const traditionalKnowledgeLabelBlock_1 = require("./traditionalKnowledgeLabelBlock");
-const updateAuthzRequest_1 = require("./updateAuthzRequest");
-const updateAuthzRequestStatus_1 = require("./updateAuthzRequestStatus");
-const updateAuthzResponse_1 = require("./updateAuthzResponse");
-const updateRaidoSchemaV1Request_1 = require("./updateRaidoSchemaV1Request");
-const updateRaidoSchemaV2Request_1 = require("./updateRaidoSchemaV2Request");
 const validationFailure_1 = require("./validationFailure");
 const validationFailureResponse_1 = require("./validationFailureResponse");
-const versionResult_1 = require("./versionResult");
 /* tslint:disable:no-unused-variable */
 let primitives = [
     "string",
@@ -220,106 +106,48 @@ let primitives = [
     "number",
     "any"
 ];
-let enumsMap = {
-    "AccessType": accessType_1.AccessType,
-    "AuthzRequestStatus": authzRequestStatus_1.AuthzRequestStatus,
-    "ContributorIdentifierSchemeType": contributorIdentifierSchemeType_1.ContributorIdentifierSchemeType,
-    "ContributorPositionRaidMetadataSchemaType": contributorPositionRaidMetadataSchemaType_1.ContributorPositionRaidMetadataSchemaType,
-    "ContributorPositionSchemeType": contributorPositionSchemeType_1.ContributorPositionSchemeType,
-    "ContributorRoleCreditNisoOrgType": contributorRoleCreditNisoOrgType_1.ContributorRoleCreditNisoOrgType,
-    "ContributorRoleSchemeType": contributorRoleSchemeType_1.ContributorRoleSchemeType,
-    "DescriptionType": descriptionType_1.DescriptionType,
-    "OrganisationIdentifierSchemeType": organisationIdentifierSchemeType_1.OrganisationIdentifierSchemeType,
-    "OrganisationRoleSchemeType": organisationRoleSchemeType_1.OrganisationRoleSchemeType,
-    "OrganisationRoleType": organisationRoleType_1.OrganisationRoleType,
-    "RaidoMetaschema": raidoMetaschema_1.RaidoMetaschema,
-    "RaidoMetaschemaV2": raidoMetaschemaV2_1.RaidoMetaschemaV2,
-    "TitleType": titleType_1.TitleType,
-};
+let enumsMap = {};
 let typeMap = {
     "Access": access_1.Access,
-    "AccessBlock": accessBlock_1.AccessBlock,
     "AccessStatement": accessStatement_1.AccessStatement,
-    "AccessTypeWithSchemaUri": accessTypeWithSchemaUri_1.AccessTypeWithSchemaUri,
+    "AccessType": accessType_1.AccessType,
     "AlternateIdentifier": alternateIdentifier_1.AlternateIdentifier,
-    "AlternateIdentifierBlock": alternateIdentifierBlock_1.AlternateIdentifierBlock,
     "AlternateUrl": alternateUrl_1.AlternateUrl,
-    "AlternateUrlBlock": alternateUrlBlock_1.AlternateUrlBlock,
-    "ApiKey": apiKey_1.ApiKey,
-    "AppUser": appUser_1.AppUser,
-    "AppUserExtraV1": appUserExtraV1_1.AppUserExtraV1,
-    "AuthzRequestExtraV1": authzRequestExtraV1_1.AuthzRequestExtraV1,
     "ClosedRaid": closedRaid_1.ClosedRaid,
     "Contributor": contributor_1.Contributor,
-    "ContributorBlock": contributorBlock_1.ContributorBlock,
     "ContributorPosition": contributorPosition_1.ContributorPosition,
-    "ContributorPositionWithSchemaUri": contributorPositionWithSchemaUri_1.ContributorPositionWithSchemaUri,
     "ContributorRole": contributorRole_1.ContributorRole,
-    "ContributorRoleWithSchemaUri": contributorRoleWithSchemaUri_1.ContributorRoleWithSchemaUri,
-    "DatesBlock": datesBlock_1.DatesBlock,
     "Description": description_1.Description,
-    "DescriptionBlock": descriptionBlock_1.DescriptionBlock,
-    "DescriptionTypeWithSchemaUri": descriptionTypeWithSchemaUri_1.DescriptionTypeWithSchemaUri,
+    "DescriptionType": descriptionType_1.DescriptionType,
     "FailureResponse": failureResponse_1.FailureResponse,
-    "GenerateApiTokenRequest": generateApiTokenRequest_1.GenerateApiTokenRequest,
-    "GenerateApiTokenResponse": generateApiTokenResponse_1.GenerateApiTokenResponse,
     "Id": id_1.Id,
-    "IdBlock": idBlock_1.IdBlock,
     "Language": language_1.Language,
-    "LegacyMetadataSchemaV1": legacyMetadataSchemaV1_1.LegacyMetadataSchemaV1,
-    "MigrateLegacyRaidRequest": migrateLegacyRaidRequest_1.MigrateLegacyRaidRequest,
-    "MigrateLegacyRaidRequestMintRequest": migrateLegacyRaidRequestMintRequest_1.MigrateLegacyRaidRequestMintRequest,
-    "MintRaidoSchemaV1Request": mintRaidoSchemaV1Request_1.MintRaidoSchemaV1Request,
-    "MintRaidoSchemaV1RequestMintRequest": mintRaidoSchemaV1RequestMintRequest_1.MintRaidoSchemaV1RequestMintRequest,
-    "MintResponse": mintResponse_1.MintResponse,
     "ModelDate": modelDate_1.ModelDate,
     "Organisation": organisation_1.Organisation,
-    "OrganisationBlock": organisationBlock_1.OrganisationBlock,
     "OrganisationRole": organisationRole_1.OrganisationRole,
-    "OrganisationRoleWithSchemaUri": organisationRoleWithSchemaUri_1.OrganisationRoleWithSchemaUri,
     "Owner": owner_1.Owner,
-    "PublicClosedMetadataSchemaV1": publicClosedMetadataSchemaV1_1.PublicClosedMetadataSchemaV1,
-    "PublicRaidMetadataSchemaV1": publicRaidMetadataSchemaV1_1.PublicRaidMetadataSchemaV1,
-    "PublicReadRaidMetadataResponseV1": publicReadRaidMetadataResponseV1_1.PublicReadRaidMetadataResponseV1,
-    "PublicReadRaidResponseV3": publicReadRaidResponseV3_1.PublicReadRaidResponseV3,
-    "PublicServicePoint": publicServicePoint_1.PublicServicePoint,
+    "RaidChange": raidChange_1.RaidChange,
     "RaidCreateRequest": raidCreateRequest_1.RaidCreateRequest,
     "RaidDto": raidDto_1.RaidDto,
-    "RaidListItemV2": raidListItemV2_1.RaidListItemV2,
-    "RaidListItemV3": raidListItemV3_1.RaidListItemV3,
-    "RaidListRequestV2": raidListRequestV2_1.RaidListRequestV2,
     "RaidUpdateRequest": raidUpdateRequest_1.RaidUpdateRequest,
-    "RaidoMetadataSchemaV1": raidoMetadataSchemaV1_1.RaidoMetadataSchemaV1,
-    "RaidoMetadataSchemaV2": raidoMetadataSchemaV2_1.RaidoMetadataSchemaV2,
-    "ReadRaidResponseV2": readRaidResponseV2_1.ReadRaidResponseV2,
-    "ReadRaidV2Request": readRaidV2Request_1.ReadRaidV2Request,
     "RegistrationAgency": registrationAgency_1.RegistrationAgency,
     "RelatedObject": relatedObject_1.RelatedObject,
-    "RelatedObjectBlock": relatedObjectBlock_1.RelatedObjectBlock,
     "RelatedObjectCategory": relatedObjectCategory_1.RelatedObjectCategory,
     "RelatedObjectType": relatedObjectType_1.RelatedObjectType,
     "RelatedRaid": relatedRaid_1.RelatedRaid,
-    "RelatedRaidBlock": relatedRaidBlock_1.RelatedRaidBlock,
     "RelatedRaidType": relatedRaidType_1.RelatedRaidType,
     "ServicePoint": servicePoint_1.ServicePoint,
+    "ServicePointCreateRequest": servicePointCreateRequest_1.ServicePointCreateRequest,
+    "ServicePointUpdateRequest": servicePointUpdateRequest_1.ServicePointUpdateRequest,
     "SpatialCoverage": spatialCoverage_1.SpatialCoverage,
-    "SpatialCoverageBlock": spatialCoverageBlock_1.SpatialCoverageBlock,
+    "SpatialCoveragePlace": spatialCoveragePlace_1.SpatialCoveragePlace,
     "Subject": subject_1.Subject,
-    "SubjectBlock": subjectBlock_1.SubjectBlock,
     "SubjectKeyword": subjectKeyword_1.SubjectKeyword,
     "Title": title_1.Title,
-    "TitleBlock": titleBlock_1.TitleBlock,
-    "TitleTypeWithSchemaUri": titleTypeWithSchemaUri_1.TitleTypeWithSchemaUri,
+    "TitleType": titleType_1.TitleType,
     "TraditionalKnowledgeLabel": traditionalKnowledgeLabel_1.TraditionalKnowledgeLabel,
-    "TraditionalKnowledgeLabelBlock": traditionalKnowledgeLabelBlock_1.TraditionalKnowledgeLabelBlock,
-    "UpdateAuthzRequest": updateAuthzRequest_1.UpdateAuthzRequest,
-    "UpdateAuthzRequestStatus": updateAuthzRequestStatus_1.UpdateAuthzRequestStatus,
-    "UpdateAuthzResponse": updateAuthzResponse_1.UpdateAuthzResponse,
-    "UpdateRaidoSchemaV1Request": updateRaidoSchemaV1Request_1.UpdateRaidoSchemaV1Request,
-    "UpdateRaidoSchemaV2Request": updateRaidoSchemaV2Request_1.UpdateRaidoSchemaV2Request,
     "ValidationFailure": validationFailure_1.ValidationFailure,
     "ValidationFailureResponse": validationFailureResponse_1.ValidationFailureResponse,
-    "VersionResult": versionResult_1.VersionResult,
 };
 class ObjectSerializer {
     static findCorrectType(data, expectedType) {

package/dist/model/organisation.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org
@@ -31,7 +31,7 @@ class Organisation {
         {
             "name": "role",
             "baseName": "role",
-            "type": "Array<OrganisationRoleWithSchemaUri>"
+            "type": "Array<OrganisationRole>"
         }
     ];
     static getAttributeTypeMap() {

package/dist/model/organisationRole.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org
@@ -13,21 +13,21 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.OrganisationRole = void 0;
 class OrganisationRole {
-    'roleSchemeUri';
-    'role';
+    'schemaUri';
+    'id';
     'startDate';
     'endDate';
     static discriminator = undefined;
     static attributeTypeMap = [
         {
-            "name": "roleSchemeUri",
-            "baseName": "roleSchemeUri",
-            "type": "OrganisationRoleSchemeType"
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
         },
         {
-            "name": "role",
-            "baseName": "role",
-            "type": "OrganisationRoleType"
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
         },
         {
             "name": "startDate",

package/dist/model/owner.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/{raidListItemV2.js → raidChange.js}

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org
@@ -11,13 +11,18 @@
  * Do not edit the class manually.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.RaidListItemV2 = void 0;
-class RaidListItemV2 {
+exports.RaidChange = void 0;
+class RaidChange {
     'handle';
-    'primaryTitle';
-    'startDate';
-    'createDate';
-    'metadataSchema';
+    'version';
+    /**
+    * A base64 encoded json patch (RFC 6902) representation of a change to the raid.
+    */
+    'diff';
+    /**
+    * A timestamp of the change
+    */
+    'timestamp';
     static discriminator = undefined;
     static attributeTypeMap = [
         {
@@ -26,28 +31,23 @@ class RaidListItemV2 {
             "type": "string"
         },
         {
-            "name": "primaryTitle",
-            "baseName": "primaryTitle",
-            "type": "string"
+            "name": "version",
+            "baseName": "version",
+            "type": "number"
         },
         {
-            "name": "startDate",
-            "baseName": "startDate",
+            "name": "diff",
+            "baseName": "diff",
             "type": "string"
         },
         {
-            "name": "createDate",
-            "baseName": "createDate",
+            "name": "timestamp",
+            "baseName": "timestamp",
             "type": "Date"
-        },
-        {
-            "name": "metadataSchema",
-            "baseName": "metadataSchema",
-            "type": "RaidoMetaschema"
         }
     ];
     static getAttributeTypeMap() {
-        return RaidListItemV2.attributeTypeMap;
+        return RaidChange.attributeTypeMap;
     }
 }
-exports.RaidListItemV2 = RaidListItemV2;
+exports.RaidChange = RaidChange;

package/dist/model/raidCreateRequest.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/raidDto.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/raidUpdateRequest.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/registrationAgency.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/relatedObject.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org
@@ -37,7 +37,7 @@ class RelatedObject {
         {
             "name": "category",
             "baseName": "category",
-            "type": "RelatedObjectCategory"
+            "type": "Array<RelatedObjectCategory>"
         }
     ];
     static getAttributeTypeMap() {

package/dist/model/relatedObjectCategory.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/relatedObjectType.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/relatedRaid.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/relatedRaidType.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/servicePoint.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not used in this project,  see ../idl-raid-v1). Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
+ * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application. Note that swagger ui doesn\'t currently work with our spec,  see https://github.com/swagger-api/swagger-ui/issues/7724 But the spec works fine with openapi-generator tooling.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org
@@ -19,6 +19,14 @@ class ServicePoint {
     'id';
     'name';
     'identifierOwner';
+    /**
+    * The Datacite repository id. This needs to be created in Fabrica.
+    */
+    'repositoryId';
+    /**
+    * The prefix used in the handle when minting RAiDs. Assigned when the repository is created.
+    */
+    'prefix';
     'searchContent';
     'techEmail';
     'adminEmail';
@@ -41,6 +49,16 @@ class ServicePoint {
             "baseName": "identifierOwner",
             "type": "string"
         },
+        {
+            "name": "repositoryId",
+            "baseName": "repositoryId",
+            "type": "string"
+        },
+        {
+            "name": "prefix",
+            "baseName": "prefix",
+            "type": "string"
+        },
         {
             "name": "searchContent",
             "baseName": "searchContent",