FAIRiCUBE / resource-metadata

manage information for processing/analysis resources, specifically: issue form to collect md requirements, issue template to manage codelists
https://fairicube.github.io/resource-metadata/
0 stars 0 forks source link

additional values ( for several codelists) #5

Open pebau opened 1 year ago

pebau commented 1 year ago

Have tried the request form just to study, I'd kindly ask to add these options for rasdaman datacubes:

sMorrone commented 1 year ago

Hi @pebau I am moving this post to resorce-metadata repository for consistency

cozzolinoac11 commented 1 year ago

Hi @pebau, I am adding values to the codelists and thinking whether it is better to use "Analytics" or "Analysis". For me is better "Analysis". What do you think?

pebau commented 1 year ago

@cozzolinoac11 thanks for asking - actually, I have a preference for analytics as a (today) common umbrella term for all sorts of getting insight out of the data; see also this discussion.

cozzolinoac11 commented 1 year ago

Hi @pebau I agree with you! I will update the codelists quickly.

cozzolinoac11 commented 1 year ago

Hi @pebau, regarding your observation on "Conditions for access and use", it is a good point when we refer to the input/output data. In this form, however, the license asked for concerns the analysis/processing resource and not the input/output data.

pebau commented 1 year ago

@cozzolinoac11 apologies, not sure I understand:

cozzolinoac11 commented 1 year ago

@pebau I fully agree with you regarding the licenses of the data (so, yes, no doubt we have to respect conditions they come with). In my post, I was just pointing you to the fact that this form (and this repository) is meant to collect information about the analysis/processing resources. The a/p resource (e.g. an algorithm that extracts statistics from a set of data) has its own license that is independent of the license of input/output data.

pebau commented 1 year ago

@cozzolinoac11 got it - thanks for clarifying!

KathiSchleidt commented 1 year ago

On Input Data vs. Output Data, my understanding was as follows:

cozzolinoac11 commented 1 year ago

Input and output data depend on the type of resource:

KathiSchleidt commented 1 year ago

Having different semantics behind the same fields worries me (reason I've long been questioning the Input and Output data concepts).

Also, following your logic, where would the data used by the a/p resource be provided for ML/DL models? Where would analysis results of ML/DL models be stored?

Also - where are potential updates to the a/p resource metadata being collected, is there a draft of the next version of D4.3 available somewhere?

pebau commented 1 year ago

can we maybe have an example for every situation in the catalog?

cozzolinoac11 commented 1 year ago

@pebau I just compiled the form with the two example pre-processing resources we included in D4.3.

An example of a deep learning resource is available at https://github.com/FAIRiCUBE/resource-metadata/issues/6

pebau commented 1 year ago

@cozzolinoac11 thank you, that was an interesting read. So the result of a catalog query would be a Jupyter notebook demonstrating use of the processing element, that's what I understand.

If that is correct it is easy for us to likewise provide notebooks for rasdaman use, shown on examples from the FC datacube set.