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

package/dist/model/alternateIdentifierBlock.js

@@ -0,0 +1,35 @@
+"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.
+ *
+ * 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.AlternateIdentifierBlock = void 0;
+class AlternateIdentifierBlock {
+    'alternateIdentifier';
+    'alternateIdentifierType';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "alternateIdentifier",
+            "baseName": "alternateIdentifier",
+            "type": "string"
+        },
+        {
+            "name": "alternateIdentifierType",
+            "baseName": "alternateIdentifierType",
+            "type": "string"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return AlternateIdentifierBlock.attributeTypeMap;
+    }
+}
+exports.AlternateIdentifierBlock = AlternateIdentifierBlock;

package/dist/model/alternateUrl.js

@@ -0,0 +1,29 @@
+"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.
+ *
+ * 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.AlternateUrl = void 0;
+class AlternateUrl {
+    'url';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "url",
+            "baseName": "url",
+            "type": "string"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return AlternateUrl.attributeTypeMap;
+    }
+}
+exports.AlternateUrl = AlternateUrl;

package/dist/model/alternateUrlBlock.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/apiKey.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/appUser.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/appUserExtraV1.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/authzRequestExtraV1.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/authzRequestStatus.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/closedRaid.js

@@ -0,0 +1,35 @@
+"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.
+ *
+ * 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.ClosedRaid = void 0;
+class ClosedRaid {
+    'identifier';
+    'access';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "identifier",
+            "baseName": "identifier",
+            "type": "Id"
+        },
+        {
+            "name": "access",
+            "baseName": "access",
+            "type": "Access"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return ClosedRaid.attributeTypeMap;
+    }
+}
+exports.ClosedRaid = ClosedRaid;

package/dist/model/contributor.js

@@ -0,0 +1,59 @@
+"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.
+ *
+ * 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.Contributor = void 0;
+class Contributor {
+    'id';
+    'schemaUri';
+    'position';
+    'role';
+    'leader';
+    'contact';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
+        },
+        {
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
+        },
+        {
+            "name": "position",
+            "baseName": "position",
+            "type": "Array<ContributorPositionWithSchemaUri>"
+        },
+        {
+            "name": "role",
+            "baseName": "role",
+            "type": "Array<ContributorRoleWithSchemaUri>"
+        },
+        {
+            "name": "leader",
+            "baseName": "leader",
+            "type": "boolean"
+        },
+        {
+            "name": "contact",
+            "baseName": "contact",
+            "type": "boolean"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return Contributor.attributeTypeMap;
+    }
+}
+exports.Contributor = Contributor;

package/dist/model/contributorBlock.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/contributorIdentifierSchemeType.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/contributorPositionRaidMetadataSchemaType.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/contributorPositionSchemeType.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/contributorPositionWithSchemaUri.js

@@ -0,0 +1,47 @@
+"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.
+ *
+ * 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.ContributorPositionWithSchemaUri = void 0;
+class ContributorPositionWithSchemaUri {
+    'schemaUri';
+    'id';
+    'startDate';
+    'endDate';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
+        },
+        {
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
+        },
+        {
+            "name": "startDate",
+            "baseName": "startDate",
+            "type": "string"
+        },
+        {
+            "name": "endDate",
+            "baseName": "endDate",
+            "type": "string"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return ContributorPositionWithSchemaUri.attributeTypeMap;
+    }
+}
+exports.ContributorPositionWithSchemaUri = ContributorPositionWithSchemaUri;

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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/contributorRoleCreditNisoOrgType.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/contributorRoleSchemeType.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/contributorRoleWithSchemaUri.js

@@ -0,0 +1,35 @@
+"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.
+ *
+ * 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.ContributorRoleWithSchemaUri = void 0;
+class ContributorRoleWithSchemaUri {
+    'schemaUri';
+    'id';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
+        },
+        {
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return ContributorRoleWithSchemaUri.attributeTypeMap;
+    }
+}
+exports.ContributorRoleWithSchemaUri = ContributorRoleWithSchemaUri;

package/dist/model/datesBlock.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/description.js

@@ -0,0 +1,41 @@
+"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.
+ *
+ * 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.Description = void 0;
+class Description {
+    'text';
+    'type';
+    'language';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "text",
+            "baseName": "text",
+            "type": "string"
+        },
+        {
+            "name": "type",
+            "baseName": "type",
+            "type": "DescriptionTypeWithSchemaUri"
+        },
+        {
+            "name": "language",
+            "baseName": "language",
+            "type": "Language"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return Description.attributeTypeMap;
+    }
+}
+exports.Description = Description;

package/dist/model/descriptionBlock.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/descriptionTypeWithSchemaUri.js

@@ -0,0 +1,35 @@
+"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.
+ *
+ * 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.DescriptionTypeWithSchemaUri = void 0;
+class DescriptionTypeWithSchemaUri {
+    'id';
+    'schemaUri';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
+        },
+        {
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return DescriptionTypeWithSchemaUri.attributeTypeMap;
+    }
+}
+exports.DescriptionTypeWithSchemaUri = DescriptionTypeWithSchemaUri;

package/dist/model/failureResponse.js

@@ -0,0 +1,53 @@
+"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.
+ *
+ * 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.FailureResponse = void 0;
+class FailureResponse {
+    'type';
+    'title';
+    'status';
+    'detail';
+    'instance';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "type",
+            "baseName": "type",
+            "type": "string"
+        },
+        {
+            "name": "title",
+            "baseName": "title",
+            "type": "string"
+        },
+        {
+            "name": "status",
+            "baseName": "status",
+            "type": "number"
+        },
+        {
+            "name": "detail",
+            "baseName": "detail",
+            "type": "string"
+        },
+        {
+            "name": "instance",
+            "baseName": "instance",
+            "type": "string"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return FailureResponse.attributeTypeMap;
+    }
+}
+exports.FailureResponse = FailureResponse;

package/dist/model/generateApiTokenRequest.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org

package/dist/model/generateApiTokenResponse.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 this project).
+ * 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.
  *
  * The version of the OpenAPI document: 2.0.0
  * Contact: contact@raid.org