Alex Ioannidis

Results 109 issues of Alex Ioannidis

We should not use the private field `_results` of the `RecordList` object. This field is encapsulated by the object and exposed through public properties such as `aggregations`. However, only labelled...

stale

* Closes https://github.com/zenodo/zenodo-rdm/issues/847.

There are three ways to describe a nullable/optional value right now: - Field is not there at all - Field is there but with a `null` value - Field is...

stale

When adding a new creator/contributor through the modal, for "Person"s (i.e. the default radio button choice), the usual flow goes as follows: 1. Top-most/first input field is the Names search...

ux
stale

To reproduce: 1. Create a new upload, select a community and submit for review 2. Reject the review request (as a community curator/owner) 3. Go to the upload again and...

bug
stale

When selecting licenses/rights on the deposit form, the UX might be a bit confusing: - When opening the modal, the user is presented with the initial list of the 6...

ux
stale

Write documentation for developers as the audience e.g that will include any technical design explanation

stale
documentation

- Versioning in InvenioRDM works with dedicated/stable URLs (e.g. `/api/records/{id}/draft/latest`). - In legacy we expose the absolute/resolved URL of the latest draft version (i.e. `/api/deposit/depositions/{latest_version_id}`)

While there is a structural/format validation for filled-in ORCiD values (i.e. that the string follows the `NNNN-NNNN-NNNN-NNNN` pattern), there is no [checksum verification](https://support.orcid.org/hc/en-us/articles/360006897674-Structure-of-the-ORCID-Identifier) for the ORCiD value itself, which could...

validation
user experience

- Should we include the `SecretLinkService` sub-service? - We need to implement a redirection/translation of existing secret links from legacy into the new format in InvenioRDM