RFC0021: Archive resource #35
Conversation
|
You can find some more context in this thread https://github.com/openregister/registers-rfcs/pull/12/files#r185759983 |
|
I don't think I actually understand the use case for downloading entries and items as files in a zip. And also, from what I can see in google analytics this endpoint gets no traffic at the moment. What if we just deprecated the endpoint instead? |
|
@MatMoore If I understand correctly where this endpoint comes from, it is the original way to get a full copy for a register in a single request. Internally, instead, we use RSF but RSF is not part of the specification and so far the position is that it shouldn't be standardised. So, if we remove this endpoint we accept that there is no relevant user need to get a copy for the register in a single request, which according to the metrics you mention is the case. I'm happy to discuss in person, perhaps with @gidsg so we have all points of view on the matter. |
|
Sounds good 👍 |
content/archive-resource/index.md
Outdated
|
|
||
| ## Motivation | ||
|
|
||
| Currently, the specification defines the Archive resource as a zip file withi |
Signed-off-by: Arnau Siches <arnau.siches@digital.cabinet-office.gov.uk>
Signed-off-by: Arnau Siches <arnau.siches@digital.cabinet-office.gov.uk>
Signed-off-by: Arnau Siches <arnau.siches@digital.cabinet-office.gov.uk>
Signed-off-by: Arnau Siches <arnau.siches@digital.cabinet-office.gov.uk>
arnau
force-pushed
the
archive-resource
branch
from
e7cc70e
to
478d9f9
Compare
UPDATE: After @MatMoore question on the actual purpose of the archive resource, we agreed in removing it. The new RFC reflects this decision.