Merge Conflicts

Author: ChengShi-1

.husky/pre-commit

@@ -0,0 +1,4 @@
+npm run format
+npm run typecheck
+npm run lint:fix
+git add .

CHANGELOG.md

@@ -9,15 +9,61 @@ This changelog follows the principles of [Keep a Changelog](https://keepachangel
 ### Added
 
 - Datasets: Added `updateDatasetLicense` use case and repository method to support Dataverse endpoint `PUT /datasets/{id}/license`, for updating dataset license or custom terms
+- New Use Case: [Get Collections For Linking Use Case](./docs/useCases.md#get-collections-for-linking).
+- New Use Case: [Create a Dataset Template](./docs/useCases.md#create-a-dataset-template) under Collections.
 
 ### Changed
 
 ### Fixed
 
 ### Removed
 
+- Removed date fields validations in create and update dataset use cases, since validation is already handled in the backend and SPA frontend (other clients should perform client side validation also). This avoids duplicated logic and keeps the package focused on its core responsibility.
+
+[Unreleased]: https://github.com/IQSS/dataverse-client-javascript/compare/v2.1.0...develop
+
 ---
 
-## [v2.0.0] -- 2025-07-04
+## [v2.1.0] -- 2025-09-29
+
+### Added
+
+- CHANGELOG.md file to track changes in a standard way.
+
+- New property isAdvancedSearchFieldType returned by API in GetCollectionMetadataBlocks and GetMetadataBlockByName use cases.
+
+- Use cases for Notifications: GetAllNotifications, DeleteNotification.
+
+- Use cases for Dataset Linking: LinkDataset, UnlinkDataset, GetDatasetLinkedCollections.
+
+- Use case: GetCitationInOtherFormats.
+
+- Use case: GetDatasetAvailableCategories.
+
+- Use cases for Collections Linking: LinkCollection, UnlinkCollection, GetCollectionLinks.
+
+- Use cases for External Tools: GetExternalTools, GetDatasetExternalToolResolved, GetFileExternalToolResolved.
+
+- Use case: GetDatasetTemplates.
+
+- Use case: GetAvailableStandardLicenses.
+
+- Use case: GetAvailableDatasetMetadataExportFormats.
+
+- Use cases for Dataset Types: GetDatasetAvailableDatasetTypes, GetDatasetAvailableDatasetType, AddDatasetType, LinkDatasetTypeWithMetadataBlocks, SetAvailableLicensesForDatasetType, DeleteDatasetType.
+
+### Changed
+
+- CreateDataset use case updated to allow non-default dataset types.
+
+- GetCollectionMetadataBlocks use case updated to support passing a dataset type.
+
+### Fixed
+
+- Integration tests in Roles Repository.
+
+- Incorrect Filter Queries split that caused value parts to be truncated.
+
+### Security
 
-[Unreleased]: https://github.com/IQSS/dataverse-frontend/compare/v2.0.0...develop
+- Dependencies updated to address vulnerabilities found by npm audit.

docs/making-releases.md

@@ -41,8 +41,6 @@ npm version 3.5.0 --no-git-tag-version
 
 This command will update the version in the `package.json` and `package-lock.json`.
 
-If everything looks good, you can push the changes to the repository.
-
 ## Update the changelog
 
 **Note**: Contributors should have already added their changes to the `[Unreleased]` section as part of their pull requests (see [CONTRIBUTING.md](../.github/CONTRIBUTING.md#changelog-guidelines) for details).
@@ -86,8 +84,9 @@ Before releasing, ensure the changelog is properly prepared:
    ### Removed
    ```
 
-4. **Update the version links** at the bottom of the changelog files
-5. **Commit the changelog updates** as part of the release preparation
+4. **Commit the changelog updates** as part of the release preparation
+
+If everything looks good, you can push the changes to the repository.
 
 ## Merge "release branch" into "main"
 

docs/useCases.md

@@ -16,6 +16,7 @@ The different use cases currently available in the package are classified below,
     - [List All Collection Items](#list-all-collection-items)
     - [List My Data Collection Items](#list-my-data-collection-items)
     - [Get Collection Featured Items](#get-collection-featured-items)
+    - [Get Collections for Linking](#get-collections-for-linking)
   - [Collections write use cases](#collections-write-use-cases)
     - [Create a Collection](#create-a-collection)
     - [Update a Collection](#update-a-collection)
@@ -24,6 +25,7 @@ The different use cases currently available in the package are classified below,
     - [Update Collection Featured Items](#update-collection-featured-items)
     - [Delete Collection Featured Items](#delete-collection-featured-items)
     - [Delete a Collection Featured Item](#delete-a-collection-featured-item)
+    - [Create a Dataset Template](#create-a-dataset-template)
 - [Datasets](#Datasets)
   - [Datasets read use cases](#datasets-read-use-cases)
     - [Get a Dataset](#get-a-dataset)
@@ -337,6 +339,69 @@ The `collectionIdOrAlias` is a generic collection identifier, which can be eithe
 
 If no collection identifier is specified, the default collection identifier; `:root` will be used. If you want to search for a different collection, you must add the collection identifier as a parameter in the use case call.
 
+#### Get Collections for Linking
+
+Returns an array of [CollectionSummary](../src/collections/domain/models/CollectionSummary.ts) (id, alias, displayName) representing the Dataverse collections to which a given Dataverse collection or Dataset may be linked.
+
+This use case supports an optional `searchTerm` to filter by collection name.
+
+##### Example calls:
+
+```typescript
+import { getCollectionsForLinking } from '@iqss/dataverse-client-javascript'
+
+/* ... */
+
+// Case 1: For a given Dataverse collection (by numeric id or alias)
+const collectionIdOrAlias: number | string = 'collectionAlias' // or 123
+const searchTerm = 'searchOn'
+
+getCollectionsForLinking
+  .execute('collection', collectionIdOrAlias, searchTerm)
+  .then((collections) => {
+    // collections: CollectionSummary[]
+    /* ... */
+  })
+  .catch((error: Error) => {
+    /* ... */
+  })
+
+/* ... */
+
+// Case 2: For a given Dataset (by persistent identifier)
+const persistentId = 'doi:10.5072/FK2/J8SJZB'
+
+getCollectionsForLinking
+  .execute('dataset', persistentId, searchTerm)
+  .then((collections) => {
+    // collections: CollectionSummary[]
+    /* ... */
+  })
+  .catch((error: Error) => {
+    /* ... */
+  })
+
+// Case 3: [alreadyLinked] Optional flag. When true, returns collections currently linked (candidates to unlink). Defaults to false.
+const alreadyLinked = true
+
+getCollectionsForLinking
+  .execute('dataset', persistentId, searchTerm, alreadyLinked)
+  .then((collections) => {
+    // collections: CollectionSummary[]
+    /* ... */
+  })
+  .catch((error: Error) => {
+    /* ... */
+  })
+```
+
+_See [use case](../src/collections/domain/useCases/GetCollectionsForLinking.ts) implementation_.
+
+Notes:
+
+- When the first argument is `'collection'`, the second argument can be a numeric collection id or a collection alias.
+- When the first argument is `'dataset'`, the second argument must be the dataset persistent identifier string (e.g., `doi:...`).
+
 ### Collections Write Use Cases
 
 #### Create a Collection
@@ -504,6 +569,41 @@ deleteCollectionFeaturedItem.execute(featuredItemId)
 
 _See [use case](../src/collections/domain/useCases/DeleteCollectionFeaturedItem.ts)_ definition.
 
+#### Create a Dataset Template
+
+Creates a dataset template for a given Dataverse collection id or alias.
+
+##### Example call:
+
+```typescript
+import { createDatasetTemplate } from '@iqss/dataverse-client-javascript'
+import { TemplateCreateDTO } from '@iqss/dataverse-client-javascript'
+
+const collectionAlias = ':root'
+const template: TemplateCreateDTO = {
+  name: 'Dataverse template',
+  isDefault: true,
+  fields: [
+    {
+      typeName: 'author',
+      typeClass: 'compound',
+      multiple: true,
+      value: [
+        {
+          authorName: { typeName: 'authorName', value: 'Belicheck, Bill' },
+          authorAffiliation: { typeName: 'authorIdentifierScheme', value: 'ORCID' }
+        }
+      ]
+    }
+  ],
+  instructions: [{ instructionField: 'author', instructionText: 'The author data' }]
+}
+
+await createDatasetTemplate.execute(template, collectionAlias)
+```
+
+_See [use case](../src/collections/domain/useCases/CreateDatasetTemplate.ts) implementation_.
+
 ## Datasets
 
 ### Datasets Read Use Cases
@@ -861,7 +961,7 @@ _See [use case](../src/datasets/domain/useCases/GetDatasetAvailableDatasetType.t
 
 #### Create a Dataset
 
-Creates a new Dataset in a collection, given a [DatasetDTO](../src/datasets/domain/dtos/DatasetDTO.ts) object and an optional collection identifier, which defaults to `:root`.
+Creates a new Dataset in a collection, given a [DatasetDTO](../src/datasets/domain/dtos/DatasetDTO.ts) object, an optional collection identifier, which defaults to `:root`, and an optional dataset type.
 
 This use case validates the submitted fields of each metadata block and can return errors of type [ResourceValidationError](../src/core/domain/useCases/validators/errors/ResourceValidationError.ts), which include sufficient information to determine which field value is invalid and why.
 
@@ -916,7 +1016,7 @@ createDataset.execute(datasetDTO).then((newDatasetIds: CreatedDatasetIdentifiers
 
 _See [use case](../src/datasets/domain/useCases/CreateDataset.ts) implementation_.
 
-The above example creates the new dataset in the root collection since no collection identifier is specified. If you want to create the dataset in a different collection, you must add the collection identifier as a second parameter in the use case call.
+The above example creates the new dataset in the root collection since no collection identifier is specified. If you want to create the dataset in a different collection, you must add the collection identifier as a second parameter in the use case call. If you want the dataset type to be anything other than dataset, first [check available dataset types](#get-dataset-available-dataset-types) and then add the name of the dataset type as the third parameter.
 
 The use case returns a [CreatedDatasetIdentifiers](../src/datasets/domain/models/CreatedDatasetIdentifiers.ts) object, which includes the persistent and numeric identifiers of the created dataset.
 
@@ -2050,6 +2150,8 @@ The `collectionIdOrAlias` is a generic collection identifier, which can be eithe
 
 There is a second optional parameter called `onlyDisplayedOnCreate` which indicates whether or not to return only the metadata blocks that are displayed on dataset creation. The default value is false.
 
+There is a third optional parameter called `datasetType` which will include additional fields from metadata blocks linked to the provided type, if any. Before using this parameter, you will probably want to [list available dataset types](#get-dataset-available-dataset-types) for your installation.
+
 ## Users
 
 ### Users read use cases