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

package/dist/model/organisation.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.Organisation = void 0;
+class Organisation {
+    'id';
+    'schemaUri';
+    'role';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
+        },
+        {
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
+        },
+        {
+            "name": "role",
+            "baseName": "role",
+            "type": "Array<OrganisationRoleWithSchemaUri>"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return Organisation.attributeTypeMap;
+    }
+}
+exports.Organisation = Organisation;

package/dist/model/organisationBlock.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/organisationIdentifierSchemeType.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/organisationRole.js

@@ -1,7 +1,7 @@
 "use strict";
 /**
  * RAID v2 API
- * This file is where all the endpoint paths are defined, it\'s the \"top level\' of the OpenAPI definition that links all the different files together. The `3.0` in the filename refers to this file being based on OpenAPI 3.0  as opposed to OpenAPI 3.1, which the tooling doesn\'t support yet. The `2.0.0` in the version field refers to the fact that there\'s already  a `1.0.0` used for the legacy RAiD application (not 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/organisationRoleSchemeType.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/organisationRoleType.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/organisationRoleWithSchemaUri.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.OrganisationRoleWithSchemaUri = void 0;
+class OrganisationRoleWithSchemaUri {
+    '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 OrganisationRoleWithSchemaUri.attributeTypeMap;
+    }
+}
+exports.OrganisationRoleWithSchemaUri = OrganisationRoleWithSchemaUri;

package/dist/model/owner.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.Owner = void 0;
+/**
+* The legal entity responsible for the RAiD; the ‘Owner’ of a RAiD. Analogous to a DataCite ‘Member’, has a  legal agreement with the Registration Agency.
+*/
+class Owner {
+    'id';
+    'schemaUri';
+    /**
+    * The Service Point (SP) that requested the RAiD. Analogous to a DataCite ‘Repository’. SPs belong to an owner, RAiD owners can have multiple SPs, and SPs do not need to be legal entities.
+    */
+    'servicePoint';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "id",
+            "baseName": "id",
+            "type": "string"
+        },
+        {
+            "name": "schemaUri",
+            "baseName": "schemaUri",
+            "type": "string"
+        },
+        {
+            "name": "servicePoint",
+            "baseName": "servicePoint",
+            "type": "number"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return Owner.attributeTypeMap;
+    }
+}
+exports.Owner = Owner;

package/dist/model/publicClosedMetadataSchemaV1.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/publicRaidMetadataSchemaV1.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
@@ -25,6 +25,12 @@ class PublicRaidMetadataSchemaV1 {
     'alternateUrls';
     'contributors';
     'organisations';
+    'subjects';
+    'relatedRaids';
+    'relatedObjects';
+    'alternateIdentifiers';
+    'spatialCoverages';
+    'traditionalKnowledgeLabels';
     static discriminator = undefined;
     static attributeTypeMap = [
         {
@@ -71,6 +77,36 @@ class PublicRaidMetadataSchemaV1 {
             "name": "organisations",
             "baseName": "organisations",
             "type": "Array<OrganisationBlock>"
+        },
+        {
+            "name": "subjects",
+            "baseName": "subjects",
+            "type": "Array<SubjectBlock>"
+        },
+        {
+            "name": "relatedRaids",
+            "baseName": "relatedRaids",
+            "type": "Array<RelatedRaidBlock>"
+        },
+        {
+            "name": "relatedObjects",
+            "baseName": "relatedObjects",
+            "type": "Array<RelatedObjectBlock>"
+        },
+        {
+            "name": "alternateIdentifiers",
+            "baseName": "alternateIdentifiers",
+            "type": "Array<AlternateIdentifierBlock>"
+        },
+        {
+            "name": "spatialCoverages",
+            "baseName": "spatialCoverages",
+            "type": "Array<SpatialCoverageBlock>"
+        },
+        {
+            "name": "traditionalKnowledgeLabels",
+            "baseName": "traditionalKnowledgeLabels",
+            "type": "Array<TraditionalKnowledgeLabelBlock>"
         }
     ];
     static getAttributeTypeMap() {

package/dist/model/publicReadRaidMetadataResponseV1.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
@@ -25,6 +25,12 @@ class PublicReadRaidMetadataResponseV1 {
     'alternateUrls';
     'contributors';
     'organisations';
+    'subjects';
+    'relatedRaids';
+    'relatedObjects';
+    'alternateIdentifiers';
+    'spatialCoverages';
+    'traditionalKnowledgeLabels';
     static discriminator = "metadataSchema";
     static attributeTypeMap = [
         {
@@ -71,6 +77,36 @@ class PublicReadRaidMetadataResponseV1 {
             "name": "organisations",
             "baseName": "organisations",
             "type": "Array<OrganisationBlock>"
+        },
+        {
+            "name": "subjects",
+            "baseName": "subjects",
+            "type": "Array<SubjectBlock>"
+        },
+        {
+            "name": "relatedRaids",
+            "baseName": "relatedRaids",
+            "type": "Array<RelatedRaidBlock>"
+        },
+        {
+            "name": "relatedObjects",
+            "baseName": "relatedObjects",
+            "type": "Array<RelatedObjectBlock>"
+        },
+        {
+            "name": "alternateIdentifiers",
+            "baseName": "alternateIdentifiers",
+            "type": "Array<AlternateIdentifierBlock>"
+        },
+        {
+            "name": "spatialCoverages",
+            "baseName": "spatialCoverages",
+            "type": "Array<SpatialCoverageBlock>"
+        },
+        {
+            "name": "traditionalKnowledgeLabels",
+            "baseName": "traditionalKnowledgeLabels",
+            "type": "Array<TraditionalKnowledgeLabelBlock>"
         }
     ];
     static getAttributeTypeMap() {

package/dist/model/publicReadRaidResponseV3.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/publicServicePoint.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/raidCreateRequest.js

@@ -0,0 +1,107 @@
+"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.RaidCreateRequest = void 0;
+class RaidCreateRequest {
+    'identifier';
+    'title';
+    'date';
+    'description';
+    'access';
+    'alternateUrl';
+    'contributor';
+    'organisation';
+    'subject';
+    'relatedRaid';
+    'relatedObject';
+    'alternateIdentifier';
+    'spatialCoverage';
+    'traditionalKnowledgeLabel';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "identifier",
+            "baseName": "identifier",
+            "type": "Id"
+        },
+        {
+            "name": "title",
+            "baseName": "title",
+            "type": "Array<Title>"
+        },
+        {
+            "name": "date",
+            "baseName": "date",
+            "type": "ModelDate"
+        },
+        {
+            "name": "description",
+            "baseName": "description",
+            "type": "Array<Description>"
+        },
+        {
+            "name": "access",
+            "baseName": "access",
+            "type": "Access"
+        },
+        {
+            "name": "alternateUrl",
+            "baseName": "alternateUrl",
+            "type": "Array<AlternateUrl>"
+        },
+        {
+            "name": "contributor",
+            "baseName": "contributor",
+            "type": "Array<Contributor>"
+        },
+        {
+            "name": "organisation",
+            "baseName": "organisation",
+            "type": "Array<Organisation>"
+        },
+        {
+            "name": "subject",
+            "baseName": "subject",
+            "type": "Array<Subject>"
+        },
+        {
+            "name": "relatedRaid",
+            "baseName": "relatedRaid",
+            "type": "Array<RelatedRaid>"
+        },
+        {
+            "name": "relatedObject",
+            "baseName": "relatedObject",
+            "type": "Array<RelatedObject>"
+        },
+        {
+            "name": "alternateIdentifier",
+            "baseName": "alternateIdentifier",
+            "type": "Array<AlternateIdentifier>"
+        },
+        {
+            "name": "spatialCoverage",
+            "baseName": "spatialCoverage",
+            "type": "Array<SpatialCoverage>"
+        },
+        {
+            "name": "traditionalKnowledgeLabel",
+            "baseName": "traditionalKnowledgeLabel",
+            "type": "Array<TraditionalKnowledgeLabel>"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return RaidCreateRequest.attributeTypeMap;
+    }
+}
+exports.RaidCreateRequest = RaidCreateRequest;

package/dist/model/raidDto.js

@@ -0,0 +1,107 @@
+"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.RaidDto = void 0;
+class RaidDto {
+    'identifier';
+    'title';
+    'date';
+    'description';
+    'access';
+    'alternateUrl';
+    'contributor';
+    'organisation';
+    'subject';
+    'relatedRaid';
+    'relatedObject';
+    'alternateIdentifier';
+    'spatialCoverage';
+    'traditionalKnowledgeLabel';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "identifier",
+            "baseName": "identifier",
+            "type": "Id"
+        },
+        {
+            "name": "title",
+            "baseName": "title",
+            "type": "Array<Title>"
+        },
+        {
+            "name": "date",
+            "baseName": "date",
+            "type": "ModelDate"
+        },
+        {
+            "name": "description",
+            "baseName": "description",
+            "type": "Array<Description>"
+        },
+        {
+            "name": "access",
+            "baseName": "access",
+            "type": "Access"
+        },
+        {
+            "name": "alternateUrl",
+            "baseName": "alternateUrl",
+            "type": "Array<AlternateUrl>"
+        },
+        {
+            "name": "contributor",
+            "baseName": "contributor",
+            "type": "Array<Contributor>"
+        },
+        {
+            "name": "organisation",
+            "baseName": "organisation",
+            "type": "Array<Organisation>"
+        },
+        {
+            "name": "subject",
+            "baseName": "subject",
+            "type": "Array<Subject>"
+        },
+        {
+            "name": "relatedRaid",
+            "baseName": "relatedRaid",
+            "type": "Array<RelatedRaid>"
+        },
+        {
+            "name": "relatedObject",
+            "baseName": "relatedObject",
+            "type": "Array<RelatedObject>"
+        },
+        {
+            "name": "alternateIdentifier",
+            "baseName": "alternateIdentifier",
+            "type": "Array<AlternateIdentifier>"
+        },
+        {
+            "name": "spatialCoverage",
+            "baseName": "spatialCoverage",
+            "type": "Array<SpatialCoverage>"
+        },
+        {
+            "name": "traditionalKnowledgeLabel",
+            "baseName": "traditionalKnowledgeLabel",
+            "type": "Array<TraditionalKnowledgeLabel>"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return RaidDto.attributeTypeMap;
+    }
+}
+exports.RaidDto = RaidDto;

package/dist/model/raidListItemV2.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/raidListItemV3.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.RaidListItemV3 = void 0;
+class RaidListItemV3 {
+    'handle';
+    'primaryTitle';
+    'startDate';
+    'createDate';
+    'metadataSchema';
+    static discriminator = undefined;
+    static attributeTypeMap = [
+        {
+            "name": "handle",
+            "baseName": "handle",
+            "type": "string"
+        },
+        {
+            "name": "primaryTitle",
+            "baseName": "primaryTitle",
+            "type": "string"
+        },
+        {
+            "name": "startDate",
+            "baseName": "startDate",
+            "type": "string"
+        },
+        {
+            "name": "createDate",
+            "baseName": "createDate",
+            "type": "Date"
+        },
+        {
+            "name": "metadataSchema",
+            "baseName": "metadataSchema",
+            "type": "RaidoMetaschemaV2"
+        }
+    ];
+    static getAttributeTypeMap() {
+        return RaidListItemV3.attributeTypeMap;
+    }
+}
+exports.RaidListItemV3 = RaidListItemV3;

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