Skip to main content
Waters

What is the source of each timestamp in NuGenesis SDMS and LMS? - WKB230671

Article number: 230671

ENVIRONMENT

  • NuGenesis 9
  • NuGenesis 8

ANSWER

  • NuGenesis LMS:
    • The source of most timestamps in the NuGenesis LMS client is the system clock on the LMS server. When storing a timestamp, the server takes the current time from the server's clock, converts it to UTC, and stores the UTC timestamp in the database. When displaying the timestamp in the client, the client takes the time zone offset of the client's system clock and applies it to the UTC timestamps.
    • This information applies to timestamps in:
      • Documents, sections, Sample Management, Document templates, Instrument and Reagent inventories, User Management, and User trainings
    • For LMS audit trail reports, the server does NOT convert the stored UTC timestamp to the local time. The reports display the UTC timestamps.
    • For PDF copies of LMS documents, the timestamps - if used in a report header/footer - will be in local time or UTC, depending on the LMS system setting "Use UTC for PDF".
  • NuGenesis SDMS:
    • WebVision metadata:
      • Date/Time of Print: Taken from the system clock of the machine where the report is printed. It is the time when the print job enters the UNIFY printer's queue.
      • Date/Time of Capture: For File data projects. Taken from the system clock on the machine where the Archive Agent is running. Recorded in the .NGD files in TE_TEMP when the AA finishes processing a file, or file group, and places the files into TE_TEMP.
      • Timezone of Print: same source as Date/Time of Print, but records the UTC offset rather than a timestamp.
      • Timezone of Capture: For File Data projects. Same source as Date/Time of Capture but records a UTC offset.
      • Date/Time of Print in UTC: For Print Data projects, conversion of the Date/Time of Print to UTC.
      • Date/Time of Capture in UTC: in File Data projects, conversion of the Date/Time of Capture to UTC.
      • Date/Time of Database Insertion: recorded by the Transport Engine module of the NuGenesis RPC service when it finishes the process of uploading a printed report or archived files to SDMS. This field applies to both database storage and Managed Storage projects. The timestamp is taken from the system clock of the machine where TE uploads the files to the database. For File Data projects, this comes from the SDMS File Capture server; for Print Data projects printed via the NuGenesis RPC service, it comes from the SDMS Web Server; for Print Data projects printed via a local Oracle client, it comes from the machine where UNIFY is installed, which could be either the user's own PC or a shared server such as Citrix.
      • Timezone of Database Insertion: Same sources as "Date/Time of Database Insertion", but records the UTC offset rather than a timestamp.
    • eSignature metadata:
      • eSigned on: date/time when the button <Authenticate> is clicked. When signing through NuGenesis Preview, the date/time and time zone is pulled from the OS where Preview runs, which could be the user's client machine or a Citrix server. When signing through WebVision this date/time and time zone will be pulled from the OS of the Web Server machine.
      • Server Date/Time: Server Date/Time (UTC), but translated to local time when viewed in the client.
    • Audit Trail metadata:
      • Server Date/Time (UTC): the UTC date/time of the application server when the audit trail entry was created.
      • Client Date/Time is the Client time when the audit trail entry was created, depending on how the connection is established to the database. If it was printed via the NuGenesis RPC service, the client timezone will be the timezone of the SDMS web server. If printing via a local Oracle client, the client timezone will be the timezone of the machine where UNIFY is installed (user PC or Citrix). The values for the audit trail are when the audit entry itself is created and should be almost immediately after the insertion time.

ADDITIONAL INFORMATION

For SDMS Timestamps in Citrix Environments, refer to KCS Article "What causes SDMS database time zone discrepancies? (WKB193673).

id230671, NGLMS, NGLMSLIC, NGLMSOPT, SDMS, SDMS8, SDMS8NU, SUPISDMS, SUPNG

Not able to find a solution? Click here to request help.