atomic-server
atomic-server copied to clipboard
Importing (cloning) data from other domain
Sometimes a user wants to:
- Move data from one domain (e.g.
localhost) to something else (example.com). - Import data from another site, but clone and modify it
The current /import endpoint can probably be modified to work in these cases, too.
It can already:
- deal with
local-idresources (which don't have an@idsubject)
Proposal
- Add a
move to current domaincheckbox when importing something. When this is checked, the entire path of the resource (it'sthe/pathinhttps://example.com/the/path) is interpreted as alocal-id. I think this should be enabled by default, as in most cases, the user will want to change these external resources into something that can be used locally.