Ideally this system should be deployable on a .onion too. We should discuss the configuration of this. This is something we may want to wait on until after we have reviewed the authentication system more though.

The following defaults should be set:

• Possibly, all document types
• The to_publish field to determine what is published
• Yes/Publish as values to determine what is published
• Similar fields to those used in #3 to be included for each document

On the advanced publication view, only show the document types with data. If none have data, prompt people to add data.

Add better validation and error messages when creating archive. Particularly, check the following-

• No number after space in human readable name
• No spaces or illegal chars in subdomain
• Subdomain does not exist already
• Subdomain not nil
• Archive name not nil
• Sanitize all input fields

And add specific error messages for each of these issues.

On the publish view, provide select all options for the following-

• Types to publish
• Facets values (ensure only selects all for values for chosen category)
• Fields to publish

Also clean up the view a bit

We need a way to backup the data in Archive VMs

Right now the themes we have are ones for specific archives. There should be several default themes (with their own icons) that people can choose from for their archives instead. These should be added to the list of themes AA is pulling from.

Support shutting down the public archive

Make it clearer that the email field is optional for new users

We need to figure out the best way to update the software in Archive VMs

Change the subdomain public archive is available at if the user edits it.

The existing publication form should be cleaned up and kept, but only as an advanced form. A simpler publication form, likely simply a button, should be created. It should have the following defaults-

• Publish all types where there is data
• Use to_publish to determine what is published. Publish anything with "Yes" or "Publish" or similar
• Publish most fields. This could default to all minus certain fields like ocr_status or document versions, or it could be preset in the dataspec.

People seem to be confused by the create archive button. Figure out a way to may this first step clearer.

Link to the LG add entities form as a way to add data on the archive show page.

Automatically suggest subdomain based on the archive name users enter.

We need to determine when this is triggered and ensure the documents end up in the right place.

Certain fields should be hidden from the advanced publication form like document versions. These may be the same fields as are not included in default publication settings (#3) or they may be different.

Check that the shutting down Archive VMs automatically after a timeout works properly and they start again correctly.

Encrypt archive VMs to a password provided by the user. This isn't an immediate priority, but is something that we should do after the immediate priorities are complete.

Ensure users have selected document types to publish, and then for each type have chosen:

1. The field to use to determine what should be published
2. Values that indicate docs should be published
3. Fields to include in published documents

If the users haven't chosen these, show an error and don't trigger publication.

Run public archives on a separate server and update the scripts to work with this. If needed we can build something to watch for instructions to start/stop archives, which could also be useful if we wanted to run private archives across multiple servers (for security or resource reasons).

Support deleting public archive. This gets a bit tricky as we don't want to be able to do this, but we want users to be able to do this.

Smoothly, automatically restart archives when:

1. Someone clicks link from AA
2. Someone tries to edit or publish archive

If someone tries to visit link when archive is shutdown, find way to redirect and start automatically.

The already published instance should be updated, not overwritten

Add the ability to add icons and logos to archives. It is possible that this should be handled on LG instead of AA.

Add an invite token system for test users.