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

package/dist/api/{raidoStableV1Api.js → servicePointApi.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
@@ -14,7 +14,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
     return (mod && mod.__esModule) ? mod : { "default": mod };
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.RaidoStableV1Api = exports.RaidoStableV1ApiApiKeys = void 0;
+exports.ServicePointApi = exports.ServicePointApiApiKeys = void 0;
 const request_1 = __importDefault(require("request"));
 const models_1 = require("../model/models");
 const models_2 = require("../model/models");
@@ -23,10 +23,10 @@ let defaultBasePath = 'https://api.prod.raid.org.au';
 // ===============================================
 // This file is autogenerated - Please do not edit
 // ===============================================
-var RaidoStableV1ApiApiKeys;
-(function (RaidoStableV1ApiApiKeys) {
-})(RaidoStableV1ApiApiKeys = exports.RaidoStableV1ApiApiKeys || (exports.RaidoStableV1ApiApiKeys = {}));
-class RaidoStableV1Api {
+var ServicePointApiApiKeys;
+(function (ServicePointApiApiKeys) {
+})(ServicePointApiApiKeys = exports.ServicePointApiApiKeys || (exports.ServicePointApiApiKeys = {}));
+class ServicePointApi {
     _basePath = defaultBasePath;
     _defaultHeaders = {};
     _useQuerystring = false;
@@ -66,7 +66,7 @@ class RaidoStableV1Api {
         this.authentications.default = auth;
     }
     setApiKey(key, value) {
-        this.authentications[RaidoStableV1ApiApiKeys[key]].apiKey = value;
+        this.authentications[ServicePointApiApiKeys[key]].apiKey = value;
     }
     set accessToken(accessToken) {
         this.authentications.bearerAuth.accessToken = accessToken;
@@ -76,11 +76,10 @@ class RaidoStableV1Api {
     }
     /**
      *
-     * @summary mint a raid
-     * @param raidCreateRequest
+     * @param servicePointCreateRequest
      */
-    async createRaidV1(raidCreateRequest, options = { headers: {} }) {
-        const localVarPath = this.basePath + '/raid';
+    async createServicePoint(servicePointCreateRequest, options = { headers: {} }) {
+        const localVarPath = this.basePath + '/service-point/';
         let localVarQueryParameters = {};
         let localVarHeaderParams = Object.assign({}, this._defaultHeaders);
         const produces = ['application/json'];
@@ -92,9 +91,9 @@ class RaidoStableV1Api {
             localVarHeaderParams.Accept = produces.join(',');
         }
         let localVarFormParams = {};
-        // verify required parameter 'raidCreateRequest' is not null or undefined
-        if (raidCreateRequest === null || raidCreateRequest === undefined) {
-            throw new Error('Required parameter raidCreateRequest was null or undefined when calling createRaidV1.');
+        // verify required parameter 'servicePointCreateRequest' is not null or undefined
+        if (servicePointCreateRequest === null || servicePointCreateRequest === undefined) {
+            throw new Error('Required parameter servicePointCreateRequest was null or undefined when calling createServicePoint.');
         }
         Object.assign(localVarHeaderParams, options.headers);
         let localVarUseFormData = false;
@@ -105,7 +104,7 @@ class RaidoStableV1Api {
             uri: localVarPath,
             useQuerystring: this._useQuerystring,
             json: true,
-            body: models_1.ObjectSerializer.serialize(raidCreateRequest, "RaidCreateRequest")
+            body: models_1.ObjectSerializer.serialize(servicePointCreateRequest, "ServicePointCreateRequest")
         };
         let authenticationPromise = Promise.resolve();
         if (this.authentications.bearerAuth.accessToken) {
@@ -132,7 +131,7 @@ class RaidoStableV1Api {
                     }
                     else {
                         if (response.statusCode && response.statusCode >= 200 && response.statusCode <= 299) {
-                            body = models_1.ObjectSerializer.deserialize(body, "RaidDto");
+                            body = models_1.ObjectSerializer.deserialize(body, "ServicePoint");
                             resolve({ response: response, body: body });
                         }
                         else {
@@ -145,11 +144,9 @@ class RaidoStableV1Api {
     }
     /**
      *
-     * @summary list raids
-     * @param servicePointId
      */
-    async listRaidsV1(servicePointId, options = { headers: {} }) {
-        const localVarPath = this.basePath + '/raid';
+    async findAllServicePoints(options = { headers: {} }) {
+        const localVarPath = this.basePath + '/service-point/';
         let localVarQueryParameters = {};
         let localVarHeaderParams = Object.assign({}, this._defaultHeaders);
         const produces = ['application/json'];
@@ -161,9 +158,6 @@ class RaidoStableV1Api {
             localVarHeaderParams.Accept = produces.join(',');
         }
         let localVarFormParams = {};
-        if (servicePointId !== undefined) {
-            localVarQueryParameters['servicePointId'] = models_1.ObjectSerializer.serialize(servicePointId, "number");
-        }
         Object.assign(localVarHeaderParams, options.headers);
         let localVarUseFormData = false;
         let localVarRequestOptions = {
@@ -199,7 +193,7 @@ class RaidoStableV1Api {
                     }
                     else {
                         if (response.statusCode && response.statusCode >= 200 && response.statusCode <= 299) {
-                            body = models_1.ObjectSerializer.deserialize(body, "Array<RaidDto>");
+                            body = models_1.ObjectSerializer.deserialize(body, "Array<ServicePoint>");
                             resolve({ response: response, body: body });
                         }
                         else {
@@ -212,14 +206,11 @@ class RaidoStableV1Api {
     }
     /**
      *
-     * @summary read a raid, caller must be authorized
-     * @param prefix Prefix of the raid handle
-     * @param suffix Suffix of the raid handle
+     * @param id The id of the service point
      */
-    async readRaidV1(prefix, suffix, options = { headers: {} }) {
-        const localVarPath = this.basePath + '/raid/{prefix}/{suffix}'
-            .replace('{' + 'prefix' + '}', encodeURIComponent(String(prefix)))
-            .replace('{' + 'suffix' + '}', encodeURIComponent(String(suffix)));
+    async findServicePointById(id, options = { headers: {} }) {
+        const localVarPath = this.basePath + '/service-point/{id}'
+            .replace('{' + 'id' + '}', encodeURIComponent(String(id)));
         let localVarQueryParameters = {};
         let localVarHeaderParams = Object.assign({}, this._defaultHeaders);
         const produces = ['application/json'];
@@ -231,13 +222,9 @@ class RaidoStableV1Api {
             localVarHeaderParams.Accept = produces.join(',');
         }
         let localVarFormParams = {};
-        // verify required parameter 'prefix' is not null or undefined
-        if (prefix === null || prefix === undefined) {
-            throw new Error('Required parameter prefix was null or undefined when calling readRaidV1.');
-        }
-        // verify required parameter 'suffix' is not null or undefined
-        if (suffix === null || suffix === undefined) {
-            throw new Error('Required parameter suffix was null or undefined when calling readRaidV1.');
+        // verify required parameter 'id' is not null or undefined
+        if (id === null || id === undefined) {
+            throw new Error('Required parameter id was null or undefined when calling findServicePointById.');
         }
         Object.assign(localVarHeaderParams, options.headers);
         let localVarUseFormData = false;
@@ -274,7 +261,7 @@ class RaidoStableV1Api {
                     }
                     else {
                         if (response.statusCode && response.statusCode >= 200 && response.statusCode <= 299) {
-                            body = models_1.ObjectSerializer.deserialize(body, "RaidDto");
+                            body = models_1.ObjectSerializer.deserialize(body, "ServicePoint");
                             resolve({ response: response, body: body });
                         }
                         else {
@@ -287,14 +274,12 @@ class RaidoStableV1Api {
     }
     /**
      *
-     * @param prefix Prefix of the raid handle
-     * @param suffix Suffix of the raid handle
-     * @param raidUpdateRequest
+     * @param id The id of the service point
+     * @param servicePointUpdateRequest
      */
-    async updateRaidV1(prefix, suffix, raidUpdateRequest, options = { headers: {} }) {
-        const localVarPath = this.basePath + '/raid/{prefix}/{suffix}'
-            .replace('{' + 'prefix' + '}', encodeURIComponent(String(prefix)))
-            .replace('{' + 'suffix' + '}', encodeURIComponent(String(suffix)));
+    async updateServicePoint(id, servicePointUpdateRequest, options = { headers: {} }) {
+        const localVarPath = this.basePath + '/service-point/{id}'
+            .replace('{' + 'id' + '}', encodeURIComponent(String(id)));
         let localVarQueryParameters = {};
         let localVarHeaderParams = Object.assign({}, this._defaultHeaders);
         const produces = ['application/json'];
@@ -306,17 +291,13 @@ class RaidoStableV1Api {
             localVarHeaderParams.Accept = produces.join(',');
         }
         let localVarFormParams = {};
-        // verify required parameter 'prefix' is not null or undefined
-        if (prefix === null || prefix === undefined) {
-            throw new Error('Required parameter prefix was null or undefined when calling updateRaidV1.');
-        }
-        // verify required parameter 'suffix' is not null or undefined
-        if (suffix === null || suffix === undefined) {
-            throw new Error('Required parameter suffix was null or undefined when calling updateRaidV1.');
+        // verify required parameter 'id' is not null or undefined
+        if (id === null || id === undefined) {
+            throw new Error('Required parameter id was null or undefined when calling updateServicePoint.');
         }
-        // verify required parameter 'raidUpdateRequest' is not null or undefined
-        if (raidUpdateRequest === null || raidUpdateRequest === undefined) {
-            throw new Error('Required parameter raidUpdateRequest was null or undefined when calling updateRaidV1.');
+        // verify required parameter 'servicePointUpdateRequest' is not null or undefined
+        if (servicePointUpdateRequest === null || servicePointUpdateRequest === undefined) {
+            throw new Error('Required parameter servicePointUpdateRequest was null or undefined when calling updateServicePoint.');
         }
         Object.assign(localVarHeaderParams, options.headers);
         let localVarUseFormData = false;
@@ -327,7 +308,7 @@ class RaidoStableV1Api {
             uri: localVarPath,
             useQuerystring: this._useQuerystring,
             json: true,
-            body: models_1.ObjectSerializer.serialize(raidUpdateRequest, "RaidUpdateRequest")
+            body: models_1.ObjectSerializer.serialize(servicePointUpdateRequest, "ServicePointUpdateRequest")
         };
         let authenticationPromise = Promise.resolve();
         if (this.authentications.bearerAuth.accessToken) {
@@ -354,7 +335,7 @@ class RaidoStableV1Api {
                     }
                     else {
                         if (response.statusCode && response.statusCode >= 200 && response.statusCode <= 299) {
-                            body = models_1.ObjectSerializer.deserialize(body, "RaidDto");
+                            body = models_1.ObjectSerializer.deserialize(body, "ServicePoint");
                             resolve({ response: response, body: body });
                         }
                         else {
@@ -366,4 +347,4 @@ class RaidoStableV1Api {
         });
     }
 }
-exports.RaidoStableV1Api = RaidoStableV1Api;
+exports.ServicePointApi = ServicePointApi;

package/dist/model/access.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
@@ -14,7 +14,7 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.Access = void 0;
 class Access {
     'type';
-    'accessStatement';
+    'statement';
     /**
     * Date the embargo on access to the RAiD ends. Year
     */
@@ -24,11 +24,11 @@ class Access {
         {
             "name": "type",
             "baseName": "type",
-            "type": "AccessTypeWithSchemaUri"
+            "type": "AccessType"
         },
         {
-            "name": "accessStatement",
-            "baseName": "accessStatement",
+            "name": "statement",
+            "baseName": "statement",
             "type": "AccessStatement"
         },
         {

package/dist/model/accessStatement.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/accessType.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
@@ -12,8 +12,24 @@
  */
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.AccessType = void 0;
-var AccessType;
-(function (AccessType) {
-    AccessType[AccessType["Open"] = 'Open'] = "Open";
-    AccessType[AccessType["Closed"] = 'Closed'] = "Closed";
-})(AccessType = exports.AccessType || (exports.AccessType = {}));
+class AccessType {
+    'id';
+    'schemaUri';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
+        },
+        {
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return AccessType.attributeTypeMap;
+    }
+}
+exports.AccessType = AccessType;

package/dist/model/alternateIdentifier.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/alternateUrl.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/closedRaid.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/contributor.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
@@ -34,12 +34,12 @@ class Contributor {
         {
             "name": "position",
             "baseName": "position",
-            "type": "Array<ContributorPositionWithSchemaUri>"
+            "type": "Array<ContributorPosition>"
         },
         {
             "name": "role",
             "baseName": "role",
-            "type": "Array<ContributorRoleWithSchemaUri>"
+            "type": "Array<ContributorRole>"
         },
         {
             "name": "leader",

package/dist/model/contributorPosition.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.ContributorPosition = void 0;
 class ContributorPosition {
-    'positionSchemaUri';
-    'position';
+    'schemaUri';
+    'id';
     'startDate';
     'endDate';
     static discriminator = undefined;
     static attributeTypeMap = [
         {
-            "name": "positionSchemaUri",
-            "baseName": "positionSchemaUri",
-            "type": "ContributorPositionSchemeType"
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
         },
         {
-            "name": "position",
-            "baseName": "position",
-            "type": "ContributorPositionRaidMetadataSchemaType"
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
         },
         {
             "name": "startDate",

package/dist/model/contributorRole.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,19 +13,19 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.ContributorRole = void 0;
 class ContributorRole {
-    'roleSchemeUri';
-    'role';
+    'schemaUri';
+    'id';
     static discriminator = undefined;
     static attributeTypeMap = [
         {
-            "name": "roleSchemeUri",
-            "baseName": "roleSchemeUri",
-            "type": "ContributorRoleSchemeType"
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
         },
         {
-            "name": "role",
-            "baseName": "role",
-            "type": "ContributorRoleCreditNisoOrgType"
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
         }
     ];
     static getAttributeTypeMap() {

package/dist/model/description.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
@@ -26,7 +26,7 @@ class Description {
         {
             "name": "type",
             "baseName": "type",
-            "type": "DescriptionTypeWithSchemaUri"
+            "type": "DescriptionType"
         },
         {
             "name": "language",

package/dist/model/descriptionType.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
@@ -12,8 +12,24 @@
  */
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.DescriptionType = void 0;
-var DescriptionType;
-(function (DescriptionType) {
-    DescriptionType[DescriptionType["PrimaryDescription"] = 'Primary Description'] = "PrimaryDescription";
-    DescriptionType[DescriptionType["AlternativeDescription"] = 'Alternative Description'] = "AlternativeDescription";
-})(DescriptionType = exports.DescriptionType || (exports.DescriptionType = {}));
+class DescriptionType {
+    'id';
+    'schemaUri';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
+        },
+        {
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return DescriptionType.attributeTypeMap;
+    }
+}
+exports.DescriptionType = DescriptionType;

package/dist/model/failureResponse.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/id.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
@@ -24,10 +24,6 @@ class Id {
     'registrationAgency';
     'owner';
     /**
-    * The URL for the raid via the CNRI handle system, e.g  https://hdl.handle.net/xxx.yyy/zzz
-    */
-    'globalUrl';
-    /**
     * The URL for the raid via the minting raid agency system, e.g  https://raid.org.au/10378.1/1695863
     */
     'raidAgencyUrl';
@@ -61,11 +57,6 @@ class Id {
             "baseName": "owner",
             "type": "Owner"
         },
-        {
-            "name": "globalUrl",
-            "baseName": "globalUrl",
-            "type": "string"
-        },
         {
             "name": "raidAgencyUrl",
             "baseName": "raidAgencyUrl",

package/dist/model/language.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/modelDate.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