Project

General

Profile

Actions

Feature #6832

closed

Use /packages endpoint (with Metacat 2.5.0)

Added by Lauren Walker over 7 years ago. Updated about 7 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Target version:
Start date:
08/19/2015
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:

Description

MetacatUI 1.7.2 should have the option to use Metacat 2.5.0, which will use the /packages endpoint instead of /package.

Actions #1

Updated by Lauren Walker over 7 years ago

  • Subject changed from Add option to use /packages endpoint with Metacat 2.5.0 to Use /packages endpoint (with Metacat 2.5.0)
  • Target version changed from 1.7.2 to 1.8.0

Changing to 1.8.0 since I wouldn't want to break someone's MetacatUI installation when they update to the latest 1.7.X version

Actions #2

Updated by Lauren Walker about 7 years ago

  • Status changed from New to Resolved

There are different combinations of Metacat versions, DataONE API versions, and DataONE node types (MN vs CN) that MetacatUI can use. So MetacatUI will need to check the combination in use and set the package service URL appropriately. This makes it easier for the user to configure MetacatUI - they just need to know the base URL of the MN or CN, the API version, and the Metacat version, if using Metacat.

When MetacatUI is set up for a DataONE CN, such as the instance that will be released at search.dataone.org, MetacatUI will need to check the source MN for each package, check if that MN has v2 MnRead service, and if so, then use the /packages/formatId/Id syntax using the MN's baseURL. So some packages will be available for download via MetacatUI and some won't.

Actions #3

Updated by Lauren Walker about 7 years ago

  • Target version changed from 1.8.0 to 1.12.0
Actions #4

Updated by Lauren Walker about 7 years ago

  • Target version changed from 1.12.0 to 1.9.0
Actions #5

Updated by Lauren Walker about 7 years ago

  • Target version changed from 1.9.0 to 1.8.0
Actions

Also available in: Atom PDF