How much storage space do I have on ERDA?

There's no space quota as such on the general ERDA storage, but the huge data sets known from high energy physics and bioinformatic databases are examples of data contents not considered suitable for ERDA. Anything within a few tens of terabytes should be fine, and we suggest that you just have a word with us if you want to store more than that.
ERDA also includes a file synchronization service called Seafile, and that particular part may not be so suitable for big data sets, so it comes with a quota of 100 GB per user.

Is My ERDA Data Replicated and Backed Up?

All data on ERDA is automatically replicated over multiple disks with RAID technology. We do not currently guarantee automatic and complete backup of ordinary data in your ERDA home folder or in the Workgroup shares. That would simply not make sense for the biggest data sets there. So only files explicitly duplicated with the Archive feature get backed up to tape. This includes eventual remote tape backup for extra safety. We recommend our Seafile file synchronization service for any small to medium sized data sets, for which you want automatic file versioning. With that solution you generally have the ability to recover deleted files or 'roll back' files to earlier versions.

How do I Transfer Entire Folders to/from ERDA?

In the ERDA web interface you can only upload/download individual files, so if you e.g. want to upload an entire folder structure there, first pack the folder(s) in a zip or tar file, upload it as usual and then use unpack from the right-click menu on the uploaded file.
Likewise you can use pack on a folder in ERDA, download and unpack it locally.
Alternatively you can use the efficient file/folder handling described in the Advanced Data Access sections of the user guide. That makes ERDA appear like a network drive so that you can use your local file manager to copy entire folders to ERDA.

Can I Share, Exchange and Publish Data in e.g. a Read-only Fashion on ERDA?

Yes, depending on the audience and dynamics of the data to share you can use one of three overall methods.
For permanent read-only publishing just create a new archive from your Archives page and make sure to mark it for public availability.
For more dynamic data you can either share in a read-write manner using the Workgroup shares or make them read-only in the Workgroup administration. Similarly you can do read-only sharing and publishing through the Workgroup web pages. Both are built into the Workgroups and the web pages come in a public and in a group-wide flavor, where the publishing is done by Workgroup owners storing data in the public_base and private_base workgroup subdirectories respectively on ERDA. Your Workgroups page includes links to those and to the resulting web pages.
For quick data exchange with anyone and particularly people not on ERDA, we recommend the Share Link feature. From your Files page you can create a share link for a file or folder and choose what kind of read and write access share link recipients should be granted. A similar feature applies for any data you may store in our optional Seafile data synchronization service. Just use the share by email feature to similarly create upload or download shares with optional password and time limit. Both share link methods include the option to send out an invitation with the link directly on email, but they can of course also be manually distributed by other means. Share links can also be accessed with SFTP, FTPS and WebDAVS as described in the user guide.

Is it possible to get a DOI for my ERDA archive?

Yes, since June 2018 we integrate DOI registration.
A number of users have asked about the possibility of assigning a Digital Object Identifier (DOI) to their published ERDA archives. It is getting more common to use such DOIs in research papers in line with the open-access and Open science spirit. UCPH has a license to mint DOIs through DataCite and University IT has developed a service to help do that, which we've integrated with ERDA. In practice you create your ERDA freeze archive as usual and select yes for Make Dataset Publicly Available. When satisfied with the archive contents you click Finalize archive to permanently freeze it. Afterwards you can use the Request archive DOI button on the View archive details page to proceed with the UCPH DOI registration form. At KUNet you can find a more elaborate DOI introduction including a complete visual walk-through of the process to create an archive and assign a DOI.

How Are Workgroups Managed?

Workgroups can be created by VIP and TAP employees and the creator of a workgroup automatically becomes owner. All user management is left to the owner(s) without interaction from the ERDA system administrators. Co-owners and members can be added either directly using the Swedish numberplate or email alias of the user, or indirectly if the user requests owner-/membership on the Workgroups page, and the owner(s) follow the instructions then sent on email about adding the user with the full user ID format.

Can I have a shared or separate account for our project?

No, we cannot allow such accounts or account aliasing, mainly due to rules and regulations. In case of suspected or alleged abuse we need to be able to uniquely identify who did what and when, and all kinds of anonymous or shared accounts would prevent that. Please refer to the UCPH information security policy for further details about identity and traceability requirements.
So basically you need to use your own personal and clearly identifiable account for all logins. What you can do is to use Workgroups to store data in a shared group folder. In that way the data is not bound to your account specifically and you and your project group can easily manage all account access yourselves through the Workgroup admin page.
Similarly share links can be used for access to particular subfolders if you need to e.g. automate data upload from lab machines without storing your personal login there. Please refer to the user guide for more details.

Why can't I use certain characters in file names?

ERDA prevents certain characters like "< > { | } * ? [ ]" in file names. You may already have run into similar limitations when naming files on your own PC or devices. In order to provide a secure and consistent experience across different platforms, web and advanced interfaces ERDA prohibits those and some more that are known to cause problems. Either because they are so-called control characters with a special potentially dangerous meaning on the storage systems or because they are known to interfere with the web interfacing and presentation. We are continuously evaluating the need for allowing more exotic characters but always with focus on not breaking existing interfaces and backends. Feel free to contact us about the possibility of allowing any additional characters that you may miss.

How do I install and run software XYZ in Jupyter?

We've added Jupyter integration in ERDA, so that you can run interactive data analysis sessions e.g. in a Python or R environment with direct access to all your ERDA data.
A number of software packages are already available in the different ERDA Jupyter instances, but sometimes you may still want to run additional software there. For Python and Jupyter extension packages it may work to simply install temporarily with pip or pip3 inside the session via the Terminal in the main Jupyter Launcher window, or by writing a standard Python requirements.txt file in your ERDA home and run it interactively with something like pip3 install -r requirements.txt from the Jupyter Terminal.
Please note that you need to use python2 or python3 specifically if you want to use such pip or pip3 installed packages respectively directly from the Terminal.
Alternatively you can install Python software dependencies like e.g. the scikit-image package directly in the Jupyter Notebook itself by evaluating !pip3 install scikit-image in a cell.
At the moment installing software that requires compilation or come with other external dependencies is typically not supported. We're working on a framework to allow some self-service customization of the Jupyter instances. Until then you can contact us at our support email if you have additional software wishes. Then we will see if they can be fulfilled - but we can't give any promises.

Can I get or keep an ERDA account without a UCPH account?

Yes, as long as you need an ERDA account for a project collaboration with one or more employees at UCPH it is possible to get one, even if you don't have a general UCPH account. Likewise it is possible to preserve access to your ERDA account beyond your employment at UCPH in case you need it to keep collaborating with a remaining employee.
IMPORTANT: please note that UCPH management requires all such users not employed at UCPH to explicitly register with their affiliation to a local user. So please include a reference to your associate/advisor at UCPH Science in the comment field when you fill in the OpenID or certificate account request described below.
Our general username+password access described in the user guide relies on the OpenID login from Koncern-IT / University IT and they strictly use the UCPH user database. So only users with an account there can use that login.
However, we provide two alternative access methods, namely a similar username+password login using our own separate OpenID login service, and another one relying on user certificates for added security.
You can sign up for an ERDA account with OpenID access with the Other User OpenID Signup button on the sign up page. If you already have an ERDA account and just want to enable this OpenID login before your UCPH login expires you can use the same procedure, but then you need to make sure you enter the exact same account fields in the signup form. Please ask us if in doubt.
After the ERDA admins accept your OpenID account/access request you can use your registered email address along with your chosen password for log in.
In case you want the extra secure access instead you need to request and install one of our grid certificates as described on the corresponding getting started page. As you can see in the user-cert-import guide there, the certificate install process takes quite a few steps, but then at least login gets simpler afterwards. After installing your certificate you can use it first to sign up for your ERDA account and then afterwards to log in.