Throughout the lifetime of your project, you will collect lots of data from your submitters, reviewers, attendees etc. This data is restricted and only those users who are authorised will be able to see that data.
When you get closer to your actual event, you may wish to publish some of that data so that it is available in the public domain and/or accessible to more people.
This is useful if you need to
- Publish a programme showing submissions and presenters.
- Publish data to a mobile App.
- Share data with a 3rd party.
Any of the data in your project can be published. Typically, that means submission fields such as Papers, Abstract, Title, Authors and Affiliations but it is up to you and you have total control over exactly which data is published.
Every time data is published, a Publish Version is created which contains the published data. This Publish Version can then be used in your online programme and mobile apps. Once published, the Publish Version remains unchanged, even if the original submissions and other data in your project is edited. The Publish Version is a 'snapshot' of the data in your project at a single point in time. The Publish Version is given a unique Data Version number and is marked as Published and becomes ready for downloading through the API.
Later, if the original data has changed (perhaps you've made an edit to the online programme), you may wish to re-publish your data. In this case, the original Publish Version is marked as Expired and a new Publish Version is created and marked as Published. The new Publish Version has replaced the expired Publish Version. The new Publish Version has with a new Data Version number and is ready for downloading through the API.
When the API requests published data from Firebird, it will be told the Data Version of the currently published Publish Version and so the API can make a decision on whether it has already downloaded the latest Publish Version or not and can then choose to download the updated Publish Version data as required.