Page Comparison

...

• The "type" field, which is treated identically to JSON shares as described above (note this makes sense because shared objects are always JSON)
• A "reference location" dropdown which allows the user to choose from the available databases:
  
  • Custom Plugin Collection: the first object from this custom job is shared
    • (eg the "_id" of the job can be see next to the "Title" field of the plugin manager, or the Custom - Get Jobs API call)
  • Document Metadata Collection: the document with the specified "_id" field is shared
  • Aggregated Entity Collection: the entity object with the specified "_id" field is shared
  • Aggregated Association Collection: the association object with the specified "_id" field is shared
  • Local files (see below)
• A "reference doc id" field that must contain the "_id" field of the object chosen above.
• (By contrast the "File" field is removed compared to JSON/binary shares)

Create shares that just point to the local file system

It is possible to create shares that return the local files as binary or JSON shares (on multi-node clusters, the same version of the file must be present on all nodes or unpredictable behavior will ensue). This can be used to "publish" common local files but with security restrictions.

Only administrators can use this function.

The process is similar to "Sharing an existing Infinit.e object" above, except that you should set "binary" as the type if the object is not JSON. You select "share existing object", and then:

• The "reference location" should be "Local File (admin only)"
• The "Reference doc id"  should be the absolute path of the file to be shared.

Editing existing shares

After log-in, all files you own can be seen from the top drop-down menu (initially called "Upload New File"). If you are a community owner or moderator, all files in your communities can be seen in addition. If you an administrator, all files in the system can be seen. 

...