Available from the left navigation menu, each user can maintain a basket, which is a personal list of favorite (“bookmarked”) asset collections or asset items. The basket also allows for individual or batch operations on collections in the workspace.

Users can bookmark Collections or assets for quick reference, create new versions of collections from the basket, or export .ttl or .trig files to Amazon S3 buckets for external use.

 

To add (or remove) a collection, select it and then select (or deselect) its star icon in the collection’s header, for example:

To add an asset item, select it in the collection’s editor and then select the “…” button  (More Actions) > Add to Basket.

Selecting the left-nav DASHBOARD > Basket action shows the saved elements.

Asset Collection Versioning

Multiple asset collections can be cloned and versioned together in one step, including their “includes”. To do this, place collections to clone into the basket and select the check box for the ones you would like to clone. Use the operations menu to select Create a new version.

This will bring up the versioning tool and allow you to enter the following choices.

  • Clone Includes: Checking this box will also create a new version for any included collections. In the example below, a taxonomy includes an ontology so checking this box will create a duplicate of the taxonomy and the ontology. If you do not select this box then the new taxonomy will have a reference to the same included ontology as the prior version of the taxonomy.
  • Version: This is the version stored in the metadata about the collection.
  • Keep Subject Areas: If this is checked the assigned subject area, if one is assigned will be retained on the new version of the collection.
  • Name: This is the name you would like the new version of the collection to have. You need to choose name for all “includes” as well.

Then select continue once ready. The following screen indicates success and shows you what has been created.

To see the new version number, find the metadata under the settings tab for the collection.

Export to S3

 

Setup

  1. From Server Administration in EDG, configure your S3 bucket in External System Integration Management.

Choose authentication type appropriate for your organization. https://docs.aws.amazon.com/sdk-for-java/v1/developer-guide/credentials.html#credentials-default

Test the connection after saving.

  1. In EDG Configuration, select the bucket for the default location for S3 storage for your EDG application and save.

 

Using the S3 Export

 

S3 Export uses the Basket feature of EDG.

Add your collection(s) to the Basket:

 

Navigate to the Basket:

Check the collections you want to export and select Export to S3:

Version will be added from the version metadata in the collection automatically. Change any settings here and then submit:

 

 

The export will run in the background. An Administrator can check on the status through the Server Administration – Scheduled Jobs page. Once the job completes, it is no longer listed on this page. Success or failure is logged to Tomcat logs and also notifications sent (if enabled).

 

If email is configured on the EDG application, the user who submits the export will get an email notification when it is complete.

The folders are automatically created in S3 for the type of collection that is being exported.