You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/useCases.md
+64Lines changed: 64 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,6 +16,7 @@ The different use cases currently available in the package are classified below,
16
16
-[List All Collection Items](#list-all-collection-items)
17
17
-[List My Data Collection Items](#list-my-data-collection-items)
18
18
-[Get Collection Featured Items](#get-collection-featured-items)
19
+
-[Get Collections for Linking](#get-collections-for-linking)
19
20
-[Collections write use cases](#collections-write-use-cases)
20
21
-[Create a Collection](#create-a-collection)
21
22
-[Update a Collection](#update-a-collection)
@@ -336,6 +337,69 @@ The `collectionIdOrAlias` is a generic collection identifier, which can be eithe
336
337
337
338
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.
338
339
340
+
#### Get Collections for Linking
341
+
342
+
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.
343
+
344
+
This use case supports an optional `searchTerm` to filter by collection name.
0 commit comments