ARIA Field Sets over API

ARIA has several instances where it is possible to enter data using custom fields sets. For example, the proposal and visit fields are configurable based on the access route. Review and technical review, visit feedback, etc. Selected fields are made available over several different APIs, but since they are configurable, the exact usage of these field sets vary. However, the basic concept is as follows: 1) Use a query to extract the expected fields for the context that you are submitting responses to (e.g. a proposal entry) a. For example, you may also want to add extra fields to a proposal based on visit and services selected. 2) Render these fields in order and collect user input Each field has several descriptive elements, including the type of field being rendered and how it should be configured (e.g. max characters, min / max values, etc) Each field has a REF, this is used to address the field and associate it with data on submission 3) Submit the field data back as part of whatever submission mutation is appropriate (e.g. updateProposal, or saveTechnicalReview). The exact mutation and parameter changes based on context However, the data is always submitted as an array of objects, each object contains a “ref” field and a “value” field.

Publication Details

Journal
Zenodo (CERN European Organization for Nuclear Research)
Published
2024-09-09
DOI
https://doi.org/10.5281/zenodo.13736937
Primary Topic
Software System Performance and Reliability
Type
article
Field-Weighted Citation Impact
0.00
Controls
|||
ALL TIME
JAN
FEB
MAR
APR
MAY
JUN
JUL
AUG
SEP
OCT
article

ARIA Field Sets over API

Zenodo (CERN European Organization for Nuclear Research)
Software System Performance and Reliability
article

ARIA Field Sets over API

article en

Abstract

ARIA has several instances where it is possible to enter data using custom fields sets. For example, the proposal and visit fields are configurable based on the access route. Review and technical review, visit feedback, etc. Selected fields are made available over several different APIs, but since they are configurable, the exact usage of these field sets vary. However, the basic concept is as follows: 1) Use a query to extract the expected fields for the context that you are submitting responses to (e.g. a proposal entry) a. For example, you may also want to add extra fields to a proposal based on visit and services selected. 2) Render these fields in order and collect user input Each field has several descriptive elements, including the type of field being rendered and how it should be configured (e.g. max characters, min / max values, etc) Each field has a REF, this is used to address the field and associate it with data on submission 3) Submit the field data back as part of whatever submission mutation is appropriate (e.g. updateProposal, or saveTechnicalReview). The exact mutation and parameter changes based on context However, the data is always submitted as an array of objects, each object contains a “ref” field and a “value” field.

Zenodo (CERN European Organization for Nuclear Research)
Openalex Percentile: Top 58%
Software System Performance and Reliability
AI Navigator

Ask Laika to Summarize, Analyze, and Connect papers live on the map.

Summarize Papers & Methodologies

Extract key findings, datasets, and comparative methods across publications.

Benchmark Rankings & Visual Analytics

Rank top research institutions, authors, funders, topics, and journals by Field-Weighted Citation Impact (FWCI) and paper volume with instant charts.

Connect Distant Disciplines

Bridge topological clusters on the map to find hidden collaborative intersections.