Introduction
The UPHF offers tools that allow you to store and share data, only there are several of them and each one has its own possibilities.
The purpose of this page is to explain the specifics of each tool, and to provide you with easy guidance on which tool to choose and for what use.
We have defined 4 main types of questions:
- Accessibility (local and off-site)
- Sharing (internal and external)
- Collaborative working
- The interface
The 6 tools concerned being:
You'll find a summary table below, along with explanations of the different categories:
Summary table
| Accessible locally | Off-site accessibility | Sharing possible (internal) | Sharing possible (external) | Collaborative | Web interface | |
| Cloud | Yes | Yes | Yes | Yes | Yes | Yes |
| J: | Yes | Yes but with VPN | Yes but the person must have an account on ADM | No | No | No |
| GitLab | Yes | Possibility to add members outside UPHF on a case-by-case basis | Yes | Yes if the person has an account | Asynchronous modification | Yes |
| GED | Yes | Yes | Yes | Yes | Possibility of locking a document, managing versions, comparing versions, commenting on docs, creating validation processes | Yes |
| Sakai | Yes | Yes | Yes | Yes | Documents cannot be edited directly with the platform. To modify them, you need to download them, modify them and upload them again | Yes |
| Zimbra | Yes | Yes | Yes but limited to 36mb and prohibited formats (exe, jar...) | Yes but limited to 36mb and prohibited formats (exe, jar...) | No | Yes |
Accessibility
Before you can share your file, it's important to know whether you want to access the tool from inside or outside the university.
In this case, it's very simple: the only service that is not accessible as is outside the university is the J:
disk. However, by using the university's VPN, it is possible to access it.
Sharing
We distinguish between internal sharing (among UPHF members) and external sharing (to non-UPHF members).
Internal sharing
Possible with all tools, only the J: requires the sender and recipient to have an ADM account beforehand.
If this is not the case, a request must be made by creating a ticket with the Helpdesk.
. Zimbra limits file size to 36Mb and rejects certain file types such as .exe or .jar for example.
External sharing
Impossible for the J:.
In the same way as for internal sharing,Zimbra limits file size to 36Mb and refuses certain file types such as .exe or .jar for example.
GitLab authorizes external sharing provided the recipient has an account.
Collaborative work
All possible and in many different ways with the Cloud, whether at the same time or asynchronously.
Impossible with the J: and Zimbra.
GitLab allows collaborative work, but only offline, asynchronous modification.
The GED offers a whole range of sharing options such as the ability to lock a document, manage versions, compare versions, comment on docs, create validation processes, but no real collaborative work at the same time.
For Sakai, documents can't be edited directly with the platform; to modify them, you have to upload, edit and repost.
The interface
They all have a web interface, accessible directly from ENT, except for J: which acts in the same way as a folder on your computer.