Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 13 Next »

When we display a detail of a package, we will see a screen similar to the following:

Here are the following main parts:

  1. Package title, if filled in by the sender. If not, the package ID will be displayed.

  2. Actions concerning the package, such as: Forward the package, Add recipients to the package, Edit the package and Delete the package (only those that make sense for the specific package are shown).

  3. Information about the sender and recipients of the package. If the package is private, recipients can be removed by clicking the X next to their email. After removal, they can no longer access the package.

  4. Other detailed package information, including:

    • State: It indicates the state of the package. For details, see Package states.

    • Encryption status: if the package is encrypted with the package password, it is stated so here. The administrator must enable this feature, for it to be available. For more see Encrypt the package data with the package password.

    • Package integrity: Shows the result of the last data integrity check and optionally an icon for executing a new integrity check (if the administrator enabled this). The integrity check computes current checksums for all files in the package and compares those to the original checksums computed when files were uploaded. Possible states are:

      • The integrity of the package data has not been checked yet. - Checksum not yet computed and verified.

      • The integrity of the package data is OK. - Checksum computed and verified to match.

      • The integrity of the package data is compromised. - Checksum computed and differs from the original.

      • The integrity of the package data cannot be verified. - Checksum cannot be computed (file inaccessible).

    • Package access: Shows whether the package is public, internal or private. Affects package accessibility, see description in Send a package as a logged-in user.

    • Uploaded: The date and time the package was uploaded by the sender.

    • Package ID: A unique ID that uniquely identifies a particular package.

    • Name: The name/title of the package, filled in by the sender. It is optional.

    • Total size: The total size of all package files together.

    • Password protected: Whether the package is password protected or not. If so, it cannot be accessed, and the files cannot be downloaded without entering a password.

    • Download link: A unique link for this package, under which it can be viewed and downloaded. It can be copied and sent to recipients. However, for the link to work, the recipient must fulfill the rules, see description in Send a package as a logged-in user.

    • Finally, you can see when the package is automatically deleted (expires). You will no longer be able to download it after that. The administrator may still be able to restore the package, depending on the configuration (The package is in the recycle bin.).

  5. The button allows you to download a ZIP archive containing package files. The function is suitable for packages with a large number of files, so that there is no need to download files individually. Files larger than the specified size (set by the administrator) will not be included in the ZIP archive.

  6. The icon for immediate start of a new data integrity check of all the files in the package. For details see section 4. If the package is big, the check may take a long time.

  7. List of files in the package. Click the blue file name to download the file (if the package is active – clean). Clicking the plus icon expands the detailed file information about the file. In the file integrity column, there is an icon representing the result of the last integrity check, an icon for copying the checksum of the file to the clipboard and optionally an icon for immediate start of a new data integrity check of the file (if the administrator enabled this).

Before any download of an archive or a file, the user might be requested to enter his login password again. This is specified by setting the permissions by the application administrator.

  • No labels

0 Comments

You are not logged in. Any changes you make will be marked as anonymous. You may want to Log In if you already have an account.