Publishing a document
Use on
the menu for a document to make
a URL where people from outside the project can download the most
recent version of that document ('make public web page' tab), or to
automatically upload a file to a third-party URL ('send elsewhere'
tab). Only
editors can do this.
When a document is published, you give a name to the publication details.
To publish further documents in the same way, use the 'add to
existing' tab to just choose the name so you don't have to give the
details again.
Publishing to a public web page
Publishing to a public web page is very similar to
and they make an almost identical URL. However, dead letterboxes are
folders for uploading to, but published items are
documents for downloading.
Publishing elsewhere
when first published and whenever a version is superseded,
publishing to another web site by:
- FTP: uploads the file using FTP. The URL in this case will look like
this: 'ftp://www.example.com/path/to/directory'. Don't embed the user
name and password in the URL: put them in the fields provided. The
'secret' and form fields are not used.
- HTTP POST: simulates filling in a form on a web
site which includes a file upload. This requires a certain amount of
technical knowledge about the target web site, but once set up for one
document, to do the same for others requires only choosing the name
from the 'add to existing' tab). See technical
details.
What's the name and information box for?
These appear at the top of the public folder when the visitor
follows the URL you provide to them. Remember they will not be
familiar with what the URL is for so may need some more information
about why they are being asked to submit a file. A separate name is
used so that documents from several different folders can be
published together, and also so as not to reveal too much about the
internal structure of your project.
About security
The three kinds of security allow you to control who is able to
download files from a public page.
add random code to url | Anyone who
knows the complete URL can access the public folder. However, a random
code in the URL prevents someone guessing the URL. While a stranger is
unlikely to guess the URL without the code, someone familiar with
Ensembling would know what the URL pattern is like and could make a
better stab at it, and URLs can, in principle, be examined by anone
who has access to the networks over which they are sent
(packet
sniffing). |
prompt user for pass code to get
access | Like a password, you can supply the (randomly
generated) pass code separately from the URL and the visitor must
supply it to download a file. Of course, it is still only as secure as
the distribution of the pass code. |
open access | Anyone who knows the URL
can download the files. The URL is not linked from anywhere (unless
you do this explicitly) so it won't end up in Google available to the
general public unless you deliberately do so. |
I'd like to make several files available to the recipient
After you publish the first file from a project, you can choose the
same name from a menu on the [publish] form. When you do this for a
public web page, the file will also be published in the same public
folder (with the same security settings). The recipient can choose to
download all or some of the files by ticking boxes against the
names. When you do this for publishing to a third-party site the file
is trabnsferred using the same combination of settings.
I forgot the URL
Click on the published indicator
. You can copy and paste the URL from the
form provided, test it, or have the details sent to you by email.
Why would I want the URL emailed to me?
So you can forward it to the people you want to invite to download
files.
How do I turn it off?
Click on the published indicator
and choose Make Private Again.