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

package/dist/model/servicePointCreateRequest.js

@@ -0,0 +1,104 @@
+"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. 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
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ServicePointCreateRequest = void 0;
+class ServicePointCreateRequest {
+    /**
+    * The name of the service point
+    */
+    'name';
+    /**
+    * The email address of the person responsible for administering the service point.
+    */
+    'adminEmail';
+    /**
+    * The email address of a technical contact when using the API
+    */
+    'techEmail';
+    /**
+    * The PID of the institution that will own the RAiDs (currently only RORs are supported).
+    */
+    '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';
+    /**
+    * The password of the repository in Datacite.
+    */
+    'password';
+    /**
+    * Whether users are able to edit RAiDs in the in the app. This can cause conflicts when also creating/updating RAiDs through the API.
+    */
+    'appWritesEnabled';
+    /**
+    * Whether the service point is able to create or update RAiDs
+    */
+    'enabled';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "name",
+            "baseName": "name",
+            "type": "string"
+        },
+        {
+            "name": "adminEmail",
+            "baseName": "adminEmail",
+            "type": "string"
+        },
+        {
+            "name": "techEmail",
+            "baseName": "techEmail",
+            "type": "string"
+        },
+        {
+            "name": "identifierOwner",
+            "baseName": "identifierOwner",
+            "type": "string"
+        },
+        {
+            "name": "repositoryId",
+            "baseName": "repositoryId",
+            "type": "string"
+        },
+        {
+            "name": "prefix",
+            "baseName": "prefix",
+            "type": "string"
+        },
+        {
+            "name": "password",
+            "baseName": "password",
+            "type": "string"
+        },
+        {
+            "name": "appWritesEnabled",
+            "baseName": "appWritesEnabled",
+            "type": "boolean"
+        },
+        {
+            "name": "enabled",
+            "baseName": "enabled",
+            "type": "boolean"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return ServicePointCreateRequest.attributeTypeMap;
+    }
+}
+exports.ServicePointCreateRequest = ServicePointCreateRequest;

package/dist/model/servicePointUpdateRequest.js

@@ -0,0 +1,113 @@
+"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. 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
+ *
+ * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
+ * https://openapi-generator.tech
+ * Do not edit the class manually.
+ */
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.ServicePointUpdateRequest = void 0;
+class ServicePointUpdateRequest {
+    /**
+    * The name of the service point
+    */
+    'id';
+    /**
+    * The name of the service point
+    */
+    'name';
+    /**
+    * The email address of the person responsible for administering the service point.
+    */
+    'adminEmail';
+    /**
+    * The email address of a technical contact when using the API
+    */
+    'techEmail';
+    /**
+    * The PID of the institution that will own the RAiDs (currently only RORs are supported).
+    */
+    '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';
+    /**
+    * The password of the repository in Datacite.
+    */
+    'password';
+    /**
+    * Whether users are able to edit RAiDs in the in the app. This can cause conflicts when also creating/updating RAiDs through the API.
+    */
+    'appWritesEnabled';
+    /**
+    * Whether the service point is able to create or update RAiDs
+    */
+    'enabled';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "id",
+            "baseName": "id",
+            "type": "number"
+        },
+        {
+            "name": "name",
+            "baseName": "name",
+            "type": "string"
+        },
+        {
+            "name": "adminEmail",
+            "baseName": "adminEmail",
+            "type": "string"
+        },
+        {
+            "name": "techEmail",
+            "baseName": "techEmail",
+            "type": "string"
+        },
+        {
+            "name": "identifierOwner",
+            "baseName": "identifierOwner",
+            "type": "string"
+        },
+        {
+            "name": "repositoryId",
+            "baseName": "repositoryId",
+            "type": "string"
+        },
+        {
+            "name": "prefix",
+            "baseName": "prefix",
+            "type": "string"
+        },
+        {
+            "name": "password",
+            "baseName": "password",
+            "type": "string"
+        },
+        {
+            "name": "appWritesEnabled",
+            "baseName": "appWritesEnabled",
+            "type": "boolean"
+        },
+        {
+            "name": "enabled",
+            "baseName": "enabled",
+            "type": "boolean"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return ServicePointUpdateRequest.attributeTypeMap;
+    }
+}
+exports.ServicePointUpdateRequest = ServicePointUpdateRequest;

package/dist/model/spatialCoverage.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
@@ -16,7 +16,6 @@ class SpatialCoverage {
     'id';
     'schemaUri';
     'place';
-    'language';
     static discriminator = undefined;
     static attributeTypeMap = [
         {
@@ -32,12 +31,7 @@ class SpatialCoverage {
         {
             "name": "place",
             "baseName": "place",
-            "type": "string"
-        },
-        {
-            "name": "language",
-            "baseName": "language",
-            "type": "Language"
+            "type": "Array<SpatialCoveragePlace>"
         }
     ];
     static getAttributeTypeMap() {

package/dist/model/{updateRaidoSchemaV2Request.js → spatialCoveragePlace.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,19 +11,25 @@
  * Do not edit the class manually.
  */
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.UpdateRaidoSchemaV2Request = void 0;
-class UpdateRaidoSchemaV2Request {
-    'metadata';
+exports.SpatialCoveragePlace = void 0;
+class SpatialCoveragePlace {
+    'text';
+    'language';
     static discriminator = undefined;
     static attributeTypeMap = [
         {
-            "name": "metadata",
-            "baseName": "metadata",
-            "type": "RaidoMetadataSchemaV2"
+            "name": "text",
+            "baseName": "text",
+            "type": "string"
+        },
+        {
+            "name": "language",
+            "baseName": "language",
+            "type": "Language"
         }
     ];
     static getAttributeTypeMap() {
-        return UpdateRaidoSchemaV2Request.attributeTypeMap;
+        return SpatialCoveragePlace.attributeTypeMap;
     }
 }
-exports.UpdateRaidoSchemaV2Request = UpdateRaidoSchemaV2Request;
+exports.SpatialCoveragePlace = SpatialCoveragePlace;

package/dist/model/subject.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/subjectKeyword.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/title.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
@@ -28,7 +28,7 @@ class Title {
         {
             "name": "type",
             "baseName": "type",
-            "type": "TitleTypeWithSchemaUri"
+            "type": "TitleType"
         },
         {
             "name": "startDate",

package/dist/model/titleType.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.TitleType = void 0;
-var TitleType;
-(function (TitleType) {
-    TitleType[TitleType["PrimaryTitle"] = 'Primary Title'] = "PrimaryTitle";
-    TitleType[TitleType["AlternativeTitle"] = 'Alternative Title'] = "AlternativeTitle";
-})(TitleType = exports.TitleType || (exports.TitleType = {}));
+class TitleType {
+    'id';
+    'schemaUri';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
+        },
+        {
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return TitleType.attributeTypeMap;
+    }
+}
+exports.TitleType = TitleType;

package/dist/model/traditionalKnowledgeLabel.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/validationFailure.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/validationFailureResponse.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/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@researchdatabox/raido-openapi-generated-node",
-  "version": "0.0.2",
-  "description": "Convenience lib for the autogenerated client code using https://openapi-generator.tech using https://github.com/au-research/raido/blob/0b2c660be90c3d7b673defb7cb708fc3c57377fa/api-svc/idl-raid-v2/src/raido-openapi-3.0.yaml ",
+  "version": "0.0.3",
+  "description": "Convenience lib for the autogenerated client code using https://openapi-generator.tech with https://github.com/au-research/raido/blob/735df6f752f2e1ece7656d05b830b591dc259d03/api-svc/idl-raid-v2/src/raido-openapi-3.0.yaml ",
   "main": "dist/api.js",
   "files": [
     "/dist"
@@ -9,7 +9,7 @@
   "scripts": {
     "test": "echo \"Error: no test specified\" && exit 1",
     "pregenerate": "npm install @openapitools/openapi-generator-cli -g",
-    "generate": "openapi-generator-cli generate -i https://raw.githubusercontent.com/au-research/raido/0b2c660be90c3d7b673defb7cb708fc3c57377fa/api-svc/idl-raid-v2/src/raido-openapi-3.0.yaml -g typescript-node -o ./src; node_modules/.bin/tsc"
+    "generate": "openapi-generator-cli generate -i https://raw.githubusercontent.com/au-research/raido/735df6f752f2e1ece7656d05b830b591dc259d03/api-svc/idl-raid-v2/src/raido-openapi-3.0.yaml -g typescript-node -o ./src; node_modules/.bin/tsc"
   },
   "author": "QCIF Engineering",
   "license": "GPL-3.0",