Child can replicate resource before file exists

[paulbert]

With the current workflow when we add a resource two requests are sent to CouchDB.

1. Create a new document with the JSON metadata for the resource
2. Upload the file attachment to the database

For large files there may be a long period where the JSON is on the database but there is no file. A child planet (community) could during this period replicate that document and only receive the JSON without the file.

Maybe we should only show resources with attachments in the parent view to avoid this? Or we could have a warning that the resource is not yet available?