Ticket #9332 (closed: fixed)

Opened 6 years ago

Last modified 5 years ago

Update getDataSets method in ICat4Catalog

Reported by: Jay Rainey Owned by: Jay Rainey
Priority: major Milestone: Release 3.2
Component: Framework Keywords: ICAT
Cc: nick.draper@… Blocked By:
Blocking: Tester: Alex Buts

Description

Currently, getDatasets() in ICat4Catalog does nothing. It should populate a workspace with information on all the datasets in a specific investigation (based on investigation ID).

To accomplish this I need to:

  1. Update the query to return a dataset.
  2. Update saveDataSets to save the information of the datasets returned by the above query to a workspace.

Change History

comment:1 Changed 6 years ago by Jay Rainey

  • Summary changed from Update getDataSets method to Update getDataSets method in ICat4Catalog

comment:2 Changed 6 years ago by Jay Rainey

Updated query in getDataSets & improved debug message. Refs #9332.

Changeset: 43cb8de49902c144827b28411774bfb8fabed5e4

comment:3 Changed 6 years ago by Jay Rainey

Save dataset info to a workspace. Refs #9332.

Changeset: 9e6658ace5a0f7ca3ad2529726f543b174b60c31

comment:4 Changed 6 years ago by Owen Arnold

  • Status changed from new to assigned

comment:5 Changed 6 years ago by Jay Rainey

  • Status changed from assigned to verify
  • Resolution set to fixed

This ticket deals with updating the functionality of the CatalogGetDataSets algorithm to work similar to CatalogGetDataFiles.

You will need to update the soapendpoint in Facilities.xml to:

 <soapendpoint url="https://icatdev.isis.cclrc.ac.uk/ICATService/ICAT"></soapendpoint>

This ensures you can see the example investigationID below, which I have modified to have several datasets.

To test the functionality of CatalogGetDataSets you need to manually run the algorithm. To do this:

  1. Log into the catalog (Catalog -> Login)
  2. From the Algorithms menu enter CatalogGetDataSets and click the Execute button.
  3. Enter an investigation ID (e.g. 1390028 is a good one as it has multiple datasets that I have created).
  4. Leave Session empty (it will use your sessionID by default).
  5. Enter a name for the output workspace (e.g. datasets).
  6. View the content of the workspace. You will see that there are several different datasets for this specific investigation, which is expected. You can verify against other

comment:6 Changed 6 years ago by Alex Buts

  • Status changed from verify to verifying
  • Tester set to Alex Buts

comment:7 Changed 6 years ago by Alex Buts

  • Status changed from verifying to closed

Merge remote-tracking branch 'origin/feature/9332_icat_get_data_sets'

Full changeset: d65291e3af0ccd809fd9215fa1d42d42b71f5199

comment:8 Changed 6 years ago by Alex Buts

  • Cc nick.draper@… added

The ticket works as described but dataset search fails and the algorithm fails if catalogue query returns empty run range.

Do not know on what level it all checked, but physical runs in fact are not empty for such investigations and journal viewer (https://data.isis.rl.ac.uk/journals) is able to process catalogue and return all runs for such investigations. Until this feature is fixed, catalogue search is largely useless as nobody will use it like java search engine already present on the web.

comment:9 Changed 5 years ago by Stuart Campbell

This ticket has been transferred to github issue 10175

Note: See TracTickets for help on using tickets.