Skip to content
This repository has been archived by the owner on Nov 19, 2020. It is now read-only.

Upon deletion of record checks for referring records #74

Open
kaplun opened this issue Sep 1, 2016 · 0 comments
Open

Upon deletion of record checks for referring records #74

kaplun opened this issue Sep 1, 2016 · 0 comments

Comments

@kaplun
Copy link
Contributor

kaplun commented Sep 1, 2016

@kaplun commented on Mon Nov 09 2015

We should raise a warning to the cataloguer if there is at least one link towards the record being deleted.


@jmartinm commented on Thu Sep 01 2016

This should be moved to https://github.com/inspirehep/record-editor ?


@kaplun commented on Thu Sep 01 2016

I am not sure.

record-editor is a library to edit JSON. What it means to delete a record is not defined in Invenio AFAIK, so each installation will have it's convention (e.g. set a subfield to DELETED). So somehow I see the operation of deleting a record as an additional side widget, that INSPIRE will present in the same page.


@jmartinm commented on Thu Sep 01 2016

What it means to delete a record is not defined in Invenio AFAIK

There seems to be some convention in the API:
https://github.com/inveniosoftware/invenio-records/blob/master/invenio_records/api.py#L276

So it depends if we make record-editor a more plain JSON editor or a more integrated invenio-record-editor in which case it would make sense to use invenio-records API to for example delete a record (which would be useful for all installations)


@kaplun commented on Thu Sep 01 2016

👍
This is a good point. If this is also mapped in invenio-record-rest, and this one can be augmented to raise exception in case of linked ref, then indeed we can have record-editor to simply support a deletion end point and being able to accept e.g. 403 states for Forbidden.

In this way we could keep it agnostic to Invenio, but still support this functionality.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant