Add JSON export of AtoM clipboard items
|Category:||Clipboard||Estimated time:||50.00 hours|
|Target version:||Release 2.6.0|
|Google Code Legacy ID:||Tested version:|
This feature enhancement provides AtoM users with a way of exposing clipboard data in JSON and delivering it to an external URL via HTTP POST or GET methods, so that it can be consumed and used by a third-party application. We will also be adding an administrator setting to enable/disable the feature (it will be disabled by default in new and upgraded installations), and a method of configuring the POST to a third-party system.
- Design JSON schema for clipboard data
- Add admin settings to enable and configure HTTP send methods of JSON clipboard data to third-party system
- Develop functionality to POST clipboard data to designated host in JSON format
- Merge to public branch
#14 Updated by José Raddaoui Marín about 2 years ago
Hi Mike and Dan,
Sorry to bring this up after such a long time, but I just saw this feature on a recent document and I have a couple of concerns about it:
- Why are we calling this JSON-LD? It looks to me like it's only sending the serialized slugs array.
- This is probably going to be affected by the same-origin policy. In the test you did, you're sending the clipboard to the same origin but, in a normal scenario, the slugs will be sent to a different domain. The current implementation sends the request from the browser and that will require the receiver to implement a CORS system. This could be easily avoided by sending the request from the back-end instead of from the browser and I think we should try to address that before we release this feature. Otherwise, we should add a big warning about it in the documentation.
#19 Updated by Dan Gillean almost 2 years ago
- Status changed from Feedback to Verified
- Requires documentation deleted (
Actually, setting this to verified - I'll file a different ticket for potential changes in future releases.