- Introduction
- Tutorials
- User interfaces
- Administrative settings
- Creating/founding a new database project
- Opening page
- Invitations
- Modules
- API documentation
- Install new OBM Server guide
- PWA application
- Mobile application documentation
- Developer hints
- Frequently Asked Questions
- What is OpenBioMaps?
- What is OpenBioMaps Consortium?
- How can I create/find a new database-project?
- How can I upload data?
- How can I access data?
- How can I retrieve data with my mobile phone?
- How can I sign up for an OpenBioMaps project?
- Is there a programmable interface for developers?
- What language support is available?
- How can I contribute to OpenBioMaps?
- Should I pay for anything?
- How and where does the OpenBioMaps store the data?
- Is there any backup solution?
- I lost my password, how can I get a new one?
- Pink squares appear on the map page
- What is the RUM?
- Is it possible to assign a DOI to databases?
- Where can I find the list of the existing OpenBioMaps servers?
- How to use the OpenBioMaps mobile app?
- Where can I find the OpenBioMaps R package?
- What data download options are there?
- How/where can I access photos taken in the field with the mobile app?
- How can I delete data?
- I can’t query/see data which is visible to other users
Creating/founding a new database project¶
Any member of a database can create a new database project using the “Founding new project” form.
The new database project created will be completely independent from the current project and the founder will be its owner and sole user as long as he does not invite any new members to his project.
The steps to set up a project are as follows:
Give a unique name for the project. This name will be the prefix name of your database tables and will be mostly seen in your browser URL. It is strongly recommended to use a single and short word as the project name!
It is also necessary to give a short descriptive name that will appear in the header of our database project. This is already a translatable string, i.e. we can specify it in different languages later after the project is created. It is not recommended to be too long, rather only 2-3 words.
It is necessary to write a detailed description of what the project is, and what its purpose is. This can also be modified later.
The possibilities to access and modify the data should be defined, which determines who can query and modify the data. In the case of closed projects, there are different levels of access to data after the project is created. This setting can be changed later.
You need to specify the default centre of the map page, which we can also modify later on the map-related admin interface.
Finally, you have to specify the SRID of the base map of the project (https://spatialreference.org/), which defaults to WGS84 (EPSG 4326). It is not recommended to use something else.
Once the form has been completed and submitted, the project will be created in an experimental status. This is not relevant for the functioning of the project, but rather for the information of the users.
When the project is created, you will see a message about the creation process, in which you will see the name and password of the SQL admin user of the project. Save this. You will definitely need this.
You can access the newly created project with your existing username (email) and password.
When the project is created, a data table is created (with the name we have given it) containing only the fields required by OBM. This will be the base table of our project. Once the project is created, you will be able to add your fields to the base table or create additional tables in the administrative interface.
After logging in to the project, several settings need to be made to make the project usable, such as setting up modules and creating forms.
In a nutshell, the following settings should be done:
Set up your data table(s).
Set up upload forms.
Set up an SQL query.
Set up your map interface
Set up modules for data query (e.g. text_filter, identify_points) and visualisation (results_asStable, results_buttons, results_summary).