Upload summary page

    By clicking the arrow (Figure, next to the file name) the user will return to the Upload page where all the uploads are listed with the information of each upload (Figure). By clicking on a certain row on the Uploads list the user has navigated again to the Bulk upload summary page.

    By clicking on the info sign more details of the given bulk upload process are shown.

    The user can easily download one or all the problematic structures and fixed them locally and then re-upload them with the update option, and register the whole uploaded set without errors. The update process performed based on matching submission IDs, in case of non-matching submission ID, the update attempt will be ignored. When the update is finished the number of successful and ignored structure updates appear.

    The bulk upload process is also visible on the Dashboard page, where a process indicator can be seen and the upload process can be also canceled. When the upload is finished, we are informed about it in the Bulk Uploads section. The uploaded submission are found either in the Recently Failed or in Recent Successful Submissions section of the Dashboard page. A click on a submission on the Recently Failed section will open the submission on the Submission correction page and if not registered, the submission will be moved from the Registered by me table to the Assigned to me table. Submission from the Recent Successful Submissions section is opened on the Details page. On the Dashboard only the user's own uploads are visible but on the Upload page with the SUPERVISE_UPLOAD role, the user can see other uploads initiated by other users.

    Registered compounds

    In case when a regular bulk upload process is made the successfully registered compounds appear in the Registered category.

    images/download/attachments/9241700/upload6.png images/download/attachments/9241700/upload7.png
    Registered compounds

    The list of successfully registered compounds is paginated and contains all relevant Ids (PCN, LN, LnbRef, and CN-configurable) and the info whether the compound was a newly registered one or not.

    Failed submissions

    The failed submissions are displayed categorized by error type. The erroneous submissions are categorized by the following types: operational, structural and match. A donut chart (Figure) represents the submission distributions according to the error type.

    The user can filter out the submissions by error type (Figure).

    images/download/attachments/9241700/upload4.png images/download/attachments/9241700/upload8.png
    images/download/attachments/9241700/upload9.png
    Filter options on the Pre-registration summary page

    Submissions can be downloaded, deleted or opened in the Staging area for further analysis.

    Download submissions

    All submissions or just the selected one by error type can be downloaded in SDF format.

    The downloaded submisisons within the SDF contain the following columns (12) with default settings when no additional data is provided/used:

    structure, Submission ID, SALT FINGERPRINT, MOLWEIGHT, Restricted, LNBREF, Submission source, Submission CHEMIST ID, Submission USER ID, STATUS, Submission message, Submission date

    When additional data are used, these will be also stored in the downloaded SDF.

    Update submissions

    The downloaded submissions can be corrected outside the Compound Registration system and can be later re-uploaded in an update process. The update process can be either performed in the Staging area or on the Upload Summary page.

    The submission update is not always successful, the Update submission report shows a summary of the update action:

    images/download/attachments/9241700/update3.png images/download/attachments/9241700/update2.png images/download/attachments/9241700/update1.png
    Successful submission update Partially successful submission update Failed submission update

    The Update submission can have different messages:

    Message
    OK
    Submission already processed
    Submission not found
    No salt/solvate found with ID: ...
    Salt fingerprint is in invalid format.
    "MOLWEIGHT" field is not a valid number.
    "Restricted" field is not a valid integer.
    "Submission data is invalid. The source ... is unknown

    Upload report

    The upload report in PDF contains all items from the uploaded SDF with all the relevant info. The registered structures appear in the first section of the PDF, the failed ones are after.

    The registered structures section contains: REGISTERED, structure, PCN, CN (configurable), LN, Project, SaltSolvateComposition, Parent structure existed, MF.

    NO additional data (besides Project) is displayed.

    The failing submission section contains status, structure, submission Id, Project, SaltSolvateComposition, MF.

    A PDF download confirmation window appears in case of large files: "You are about to export more than 1000 compounds, which may take longer. Are you sure you want to continue?"

    Submissions can be registered one by one from the Staging area (Submission page) or can be registered through a bulk operation from the Upload summary page with the Register All functionality

    Register All

    images/download/attachments/9241700/ready2.png
    Registering from the Upload summary page as a bulk operation

    Delete

    {info} Please be advised that the SUPERVISE_UPLOAD role should be considered an administrative elevated privilege. When project-based filtering is turned ON, users with that role can delete compounds of an upload, even if these belong to a project, they do not have access to.

    They will however remain unable to view these submission and compound entries, if they do not have access to the respective project.

    From version 20.8.0-2005111440 there is a possibility to delete bulk uploaded files, not just the submissions, but also the registered structures, in case they were not modified since the upload.

    This feature can be found on Upload report page in the top right corner.

    images/download/attachments/9241700/bulk_delete.png
    Delete from the Upload summary page as a bulk operation

    Necessary role to ‘delete all from staging’ in case of your own uploads:

    DELETE_SUBMISSION

    Necessary role to ‘delete all structures’ in case of your own uploads (it means deletion of submissions from staging and registered structures):

    DELETE_SUBMISSION

    DELETE_ID

    Necessary role to ‘delete all from staging’ in case of others” uploads:

    DELETE_SUBMISSION

    SUPERVISE_UPLOAD

    Necessary role to ‘delete all structures’ in case of others’ uploads (it means deletion of submissions from staging and registered structures):

    DELETE_SUBMISSION

    DELETE_ID

    SUPERVISE_UPLOAD

    -Delete all from staging: With the help of this function you can delete all submissions from staging that were created during this bulk upload.

    -Delete all structures: With the help of this function you can delete all submissions from staging and all registered structures that were created during this bulk upload. Registered structures can be only deleted if they were not modified since the upload.

    • Uploaded structure cannot be bulk deleted if it was amended: the parent/version/lot structure or additional data has been modified.

    • If the uploaded lot has been moved to another tree, the original parent and version created during the bulk upload will be deleted, but the moved lot will remain in the system.

    • Parent and version that was created during the bulk upload will not be deleted if a new lot has been registered to the tree since the bulk upload.

      After the deletion a report summarizes the result. If a parent/lot cannot be deleted, the IDs will appear in this report.

      images/download/attachments/9241700/Bulk_delete_new_text.png
      Bulk delete report (some parents and lots are not deleted)

    Downstream:

    From version 20.13.0-2007060635: Bulk upload deletion is propagated to downstream.

    Before this version as a workaround please use the downstream API to publish it manually.