Match dataset and document descriptions with API responses properties

[tloubrieu-jpl]

💡 Description

See for data:

See for documents:

[tloubrieu-jpl]

@tloubrieu-jpl need to answer an email to match the properties

[tloubrieu-jpl]

@jordanpadams @jshughes , Eddie is developing a search prototype UI from the new web design.

He was provided by the web design team with templates to display datasets, documents and tools to the users and we are trying to find the matching information in the model.

@edwardbarraza there are also questions on the proposed templates.

The fields for which we are searching for a match in the PDS4 model are: Data, References: do you have more details on what is expected here ? Scientific paper citation maybe… Data, Tags: we need to elaborate how we would create the tags, I don’t see them in the PDS4 model, @jordanpadams, @jshughes ?

Documents, start_date: that does not make a lot of sense to me for a document. @edwardbarraza is that what we want to describe a document ? Otherwise for documents we have creation_date, publication_date, modification_date…. Documents, stop_date: same Documents, mission type: you could use this fields in properties "pds:Investigation_Area.pds:type" Documents, mission phase: I am not finding anything for that, @jordanpadams @jshughes would you use ? Documents, Tags: same as for data

Tools I would not try too hard on this one since it is using the legacy registry. Do we have PDS4 descriptions of the software ? I see a product class "Product Software". If we do we could load some in the new registry ?

[edwardbarraza]

I am assuming I know what you are referring to when you say Documents, start_date ; Let's use a better descriptor for the document here such as either creation date or publication_date. Not knowing how those are defined makes it difficult to decide but I think they are both better suited for a Document as opposed to start_time.

@tloubrieu-jpl if you had an image/mockup of what fields you are describing it'd be much easier for me to figure out the context you're referring to

[tloubrieu-jpl]

@eddiesarevalo can you provide the mock-up you are working on to @edwardbarraza ?

[eddiesarevalo]

Hey @edwardbarraza! Its the search prototype at https://www.figma.com/file/9y6Davo80c1cuKvPFfIcAu/Mockups?node-id=20-2992&t=DqfriSPOCA0m1MR6-0

When the search result details are opened for data and document some details are to be shown. Some of these are available in our database and others are not. We are trying to see which are, and which we will have to add.

Thanks!

[tloubrieu-jpl]

Ticket is still blocked until design team resubmit the templates to the web mpdernization working group next Tuesday.

[jordanpadams]

@tloubrieu-jpl for where we get all the metadata, can we add this to a breakout for when I return next Tuesday? This may be something we get started on for the eve mod efforts

[tloubrieu-jpl]

Ok @jordanpadams, @edwardbarraza also wanted to submit updated templates to the Web Modernization Working Group since, for example, the document template, does not seem finalized yet, but the working group meeting has been cancelled today.

[tloubrieu-jpl]

@anilnatha is this ticket obsolete ?

[anilnatha]

@tloubrieu-jpl I think this ticket is obsolete because the design time has since revised the expanded state for all the result types shown in search. If there is still an issue with the content shown in the expanded state for any given item, let's create a new ticket to address it. Closing this ticket.