As a user, I want to see the PDS3 ids as they originally are

[tloubrieu-jpl]

Motivation

...so that I can I can recognize them

Additional Details

When the id contains / they are transformed with - because of the issues with the API transmission of the strings with / in the path but we want that to be transparent to the UI user.

See

• should be / in the search result

Acceptance Criteria

Given
When I perform a search request with PDS3 dois having / in them
Then I expect the results do show their id with the original /

Engineering Details

[tloubrieu-jpl]

The APi is actually returning the id with hyphen, see http://localhost:8085/PDS_APIs/pds_doi_api/0.1/dois?lid=*BISTATIC* (on pds-dev3)

@collinss-jpl do you see how that works. We were expecting to show the original id (with /) in the UI.

[tloubrieu-jpl]

To solve this issue:

• the API will provide a 'pds_identifier' or something else, which will be the one displayed in the UI search
• the search criteria still need to be processed on the UI side to use the DOI database identifier where / are replaced by - .

The only risk of conflict is if we have 2 identifiers like the following (HIGHLY unlikely):

• foo/bar-baz
• foo-bar-baz

we consider that will not happen.

[tloubrieu-jpl]

sqllite schema lid and vid columns are replaced by id and display-id (lid and vid are merged in the single column)

[tloubrieu-jpl]

@collinss-jpl is taking a different route to solve this ticket: the identifier will be handled in a query parameter instead of the path, as previously. That will remove the issues with / management.

He is also doing significant simplication of identifier mananagement in the code (lid+vid --> identifier).