# REFERENCE: lire.xml __( q{Email addresses to mail report to.} ); # REFERENCE: lire.xml __( q{A report output can be emailed to many addresses at the same time. Fill in this list with those. At least one address is required.} ); # REFERENCE: lire.xml __( q{Subject of email containing the report.} ); # REFERENCE: lire.xml __( q{This let you specify the subject that will appear in the generated emails, as a way of identifying the received reports.} ); # REFERENCE: lire.xml __( q{Options specific to the chosen destination file.} ); # REFERENCE: lire.xml __( q{This let you configure the different attributes (currently only one) for the generated file.} ); # REFERENCE: lire.xml __( q{File template for the report job.} ); # REFERENCE: lire.xml __( q{This is a file name template that may contain strftime(3) interpolation.} ); # REFERENCE: lire.xml __( q{Path to the gs(1) program.} ); # REFERENCE: lire.xml __( q{Path to the gzip(1) program.} ); # REFERENCE: lire.xml __( q{ImportJobs configured in the current store.} ); # REFERENCE: lire.xml __( q{Filter to apply to the log file.} ); # REFERENCE: lire.xml __( q{Some log files need preprocessing before they can be fed to the main Lire engine. A common filter is zcat to decompress files that were compressed using gzip or compress.} ); # REFERENCE: lire.xml __( q{Encoding used in the log file.} ); # REFERENCE: lire.xml __( q{Use this parameter in the case where your log file is in a different encoding than the system's default.} ); # REFERENCE: lire.xml __( q{Path to the log file that will be processed.} ); # REFERENCE: lire.xml __( q{This is the path to the log file which should be imported. That path is actually a pattern which accepts strftime(3) format specifications which will be interpolated before importing the log. For example, /var/log/apache/corp.com%Y%m%d.log.gz will be replaced with something like /var/log/apache/corp.com20040124.log.gz.} ); # REFERENCE: lire.xml __( q{Name for the ImportJob.} ); # REFERENCE: lire.xml __( q{It is needed to identify the import jobs for Lire to process them properly. Set this variable to do so.} ); # REFERENCE: lire.xml __( q{How often to import the log into the store} ); # REFERENCE: lire.xml __( q{Each ImportJob can have its own import period. Monthly and yearly cron jobs are run on the first day of the month or year. Weekly cron jobs are run on monday morning 00:00.} ); # REFERENCE: lire.xml __( q{Type of the logfile.} ); # REFERENCE: lire.xml __( q{This parameter describes the service by which the specified logfile was produced. This parameter is mandatory since Lire has no way of deducing it otherwise.} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Path to Lambda} ); # REFERENCE: lire.xml __( q{To generate DVI, PostScript or PDF reports you need Lambda which is the Omega version of LaTeX. It is bundled with the TeTeX distribution since version 0.9. See the User Manual for download locations.} ); # REFERENCE: lire.xml __( q{Replaced by logsource.} ); # REFERENCE: lire.xml __( q{Should submissions be archived?} ); # REFERENCE: lire.xml __( q{When this parameter is set, the Responder will save each submitted message to the directory specified in the 'lr_archive_dir' parameter.} ); # REFERENCE: lire.xml __( q{Location of the archive} ); # REFERENCE: lire.xml __( q{If the `lr_archive' option is enabled, this is where the requests will be archived.} ); # REFERENCE: lire.xml __( q{Font to use in charts} ); # REFERENCE: lire.xml __( q{Use this option to control the font that Ploticus will use to render characters. The available fonts depend on the image format chosen. Consult the Ploticus documentation for all the details.} ); # REFERENCE: lire.xml __( q{Directories containing DLF converter initializers (obsolete).} ); # REFERENCE: lire.xml __( q{This variable is superseded by plugins_init_path.} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Enable debugging output} ); # REFERENCE: lire.xml __( q{When this option is set, all messages of levels `debug' and `info' will be sent to stderr or to the system log - depending on how Lire is configured and if you use the lr_run wrapper to run Lire.} ); # REFERENCE: lire.xml __( q{Replaced by logsource.} ); # REFERENCE: lire.xml __( q{Directories containing filter specifications.} ); # REFERENCE: lire.xml __( q{Which CSS stylesheet should be used for your HTML reports ?} ); # REFERENCE: lire.xml __( q{It is now possible to customize the presentation of some elements of the HTML reports. The default's Lire CSS for HTML provides a good presentation but this option gives you the ability to use your own version.} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Replaced by report_output.} ); # REFERENCE: lire.xml __( q{Keep intermediate files} ); # REFERENCE: lire.xml __( q{During its operation Lire generates intermediate files that are normally removed when done with. If you wish to study or debug the way Lire works you can prevent Lire from deleting them with this option. The files will be stored in the directory set in the `TMPDIR' environment variable.} ); # REFERENCE: lire.xml __( q{LaTeX Customization} ); # REFERENCE: lire.xml __( q{This option can be used to include LaTeX code that will be inserted in LaTeX formatted reports (this also include the DVI, PS and PDF output formats). This can be use to custommize headers or fonts.} ); # REFERENCE: lire.xml __( q{Which syslog `facility' to use} ); # REFERENCE: lire.xml __( q{The standard UNIX syslog daemon has a couple of ways to categorize log messages. You can configure the syslog daemon to sort messages into different log files based on the facility tag. See the syslog.conf(5) man page for more information. You can select a syslog `facility' tag for Lire to use here.} ); # REFERENCE: lire.xml __( q{Where to send progress/debug/warning/error messages} ); # REFERENCE: lire.xml __( q{Lire can output a lot of information while it runs. If Lire runs from a batch environment such as an autoresponder or a cron job, it may be more convenient to send this data to the system log so that it may be inspected later.} ); # REFERENCE: lire.xml __( q{Standard error (terminal or redirected to a file)} ); # REFERENCE: lire.xml __( q{UNIX syslog daemon} ); # REFERENCE: lire.xml __( q{Which syslog program identifier to use} ); # REFERENCE: lire.xml __( q{The standard UNIX syslog daemon allows you to supply an identifier with which each Lire-generated log line will be marked. It's recommended that you use a short string without any spaces, for example `lire'.} ); # REFERENCE: lire.xml __( q{Which logo to display in the report headers?} ); # REFERENCE: lire.xml __( q{Some report output formats support the bundling of images (HTML, PDF, ...). It is then possible to associate a logo with those reports, such as the Lire logo (the default) or your company's, for example. This parameter can either be an image file on your local filesystem or an URL.} ); # REFERENCE: lire.xml __( q{Which URI should be pointed to by the logo displayed in your report headers?} ); # REFERENCE: lire.xml __( q{Some report output formats support the handling of hyperlinks (HTML, PDF, ...). It is then possible to associate one with the logo to be displayed in your report headers. By default, this link points to the LogReport Foundation's website. If you don't want any link, set this field to an empty value.} ); # REFERENCE: lire.xml __( q{Autoresponder disclaimer text} ); # REFERENCE: lire.xml __( q{This file is appended to email messages that are sent back by the autoresponder.} ); # REFERENCE: lire.xml __( q{Autoresponder explanation text} ); # REFERENCE: lire.xml __( q{This file is prepended to email messages that are sent back by the autoresponder.} ); # REFERENCE: lire.xml __( q{Email address to send report from.} ); # REFERENCE: lire.xml __( q{Email address in the "From" field of report emailed by the responder.} ); # REFERENCE: lire.xml __( q{Sets the Reply-To email header} ); # REFERENCE: lire.xml __( q{Email address where users of the responder should reply if different from the value set for "lr_mail_from".} ); # REFERENCE: lire.xml __( q{Autoresponder disclaimer text} ); # REFERENCE: lire.xml __( q{This plain text file is appended to email messages that are sent back by the autoresponder.} ); # REFERENCE: lire.xml __( q{Replaced by report_output.} ); # REFERENCE: lire.xml __( q{Replaced by report_output.} ); # REFERENCE: lire.xml __( q{Path to the old address.cf file.} ); # REFERENCE: lire.xml __( q{Path to the directory containing old style DLF converters.} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Replaced by report_output.} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Replaced by logsource.} ); # REFERENCE: lire.xml __( q{Directories containing report specifications.} ); # REFERENCE: lire.xml __( q{Abbreviate byte counts (Kb, Mb, ...)} ); # REFERENCE: lire.xml __( q{Makes Lire display byte counts in a legible format. Binary scales are used, so `1 Kb' means `1024 bytes'.} ); # REFERENCE: lire.xml __( q{Abbreviate numbers (Kb, Mb, ...)} ); # REFERENCE: lire.xml __( q{Makes Lire display numbers in a legible format. Decimal scales are used, so `1K' requests means `1000' requests.} ); # REFERENCE: lire.xml __( q{Abbreviate time units (minutes, hours, ...)} ); # REFERENCE: lire.xml __( q{Makes Lire display times in a legible format, using `m', `h' and `d' suffixes.} ); # REFERENCE: lire.xml __( q{Directories containing DLF schemas.} ); # REFERENCE: lire.xml __( q{Replaced by logsource.} ); # REFERENCE: lire.xml __( q{Autoresponder input spool} ); # REFERENCE: lire.xml __( q{The Lire autoresponder modules extracts log file attachments from email messages, processes the log files and e-mails the resulting report back to the sender. When the responder is enabled, it will look in this directory for incoming email messages. See the Lire User Manual for information on configuring email delivery to this directory.} ); # REFERENCE: lire.xml __( q{Autoresponder spool check interval} ); # REFERENCE: lire.xml __( q{When the responder is enabled, it will often check the spool directory for incoming email messages. You can enter the frequency in minutes here.} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Directories containing report configuration templates.} ); # REFERENCE: lire.xml __( q{Prevent Lire from being run as root} ); # REFERENCE: lire.xml __( q{It's generally a good idea to give programs only the minimum amount of privileges required to run and restrict all else. Lire does not need to run as root for normal operation and it's therefore recommended practice to run it in a dedicated UNIX account. Lire checks its user ID when it starts and aborts when it finds that it runs as root. You can disable this check here so that Lire can be run from the superuser account. Caveat emptor.} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{How are week numbers computed?} ); # REFERENCE: lire.xml __( q{With "W", week numbers range from 00 to 53, starting with the first Monday as the first day of week 01; with "U", week numbers range from 00 to 53, starting with the first Sunday as the first day of week 01 and with "ISO", week numbers are computed according to ISO 8601:1988, range 01 to 53, where week 1 is the first week that has at least 4 days in the current year, and with Monday as the first day of the week.} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Path to odvips} ); # REFERENCE: lire.xml __( q{To generate PostScript or PDF reports you need odvips which is the Omega version of dvips. It is bundled with the TeTeX distribution since version 0.9. See the User Manual for download locations.} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Path to the ploticus(1) program.} ); # REFERENCE: lire.xml __( q{Directories containing plugin initializers.} ); # REFERENCE: lire.xml __( q{A list of directories which contain initialization scripts. These are short perl script that should register plugins with the Lire::PluginManager.} ); # REFERENCE: lire.xml __( q{Path to ps2pdf} ); # REFERENCE: lire.xml __( q{To generate PDF reports you need ps2pdf. This is part of the Ghostscript distribution. See the User Manual for download locations.} ); # REFERENCE: lire.xml __( q{ReportJobs configured in the current store.} ); # REFERENCE: lire.xml __( q{Name of the ReportJob.} ); # REFERENCE: lire.xml __( q{It is needed to identify the report jobs for Lire to process them properly. Set this variable to do so. NOTE: This name should contains only alphanumeric characters, hyphens or underscores.} ); # REFERENCE: lire.xml __( q{Report Generation Schedules} ); # REFERENCE: lire.xml __( q{ReportJob's must be generated on one or more periods, each of which have to be described as a "report schedule". A report schedule let you specify which report should be formatted, following which configuration at which frequency.} ); # REFERENCE: lire.xml __( q{List of OutputJobs} ); # REFERENCE: lire.xml __( q{When reports are scheduled, they can be output in different forms and different formats. This is what OutputJobs are about and you can configure several of them for the same schedule.} ); # REFERENCE: lire.xml __( q{The target type of the output report.} ); # REFERENCE: lire.xml __( q{Lire can either save its formatted report as a file on a filesystem or send it by email to a chosen address. This option lets you configure this.} ); # REFERENCE: lire.xml __( q{Send the formatted output via email.} ); # REFERENCE: lire.xml __( q{Store the formatted output into a file.} ); # REFERENCE: lire.xml __( q{File type of the generated report} ); # REFERENCE: lire.xml __( q{Lire can format its reports in a variety of ways, from a simple plain text file to a pretty PDF file suitable for printing.} ); # REFERENCE: lire.xml __( q{Identifier} ); # REFERENCE: lire.xml __( q{An identifier for this output job.} ); # REFERENCE: lire.xml __( q{How often you want to generate the report} ); # REFERENCE: lire.xml __( q{This is the frequency by which this report schedule will be executed. The value for this parameter can be either "hourly", "daily", "weekly", "monthly" or "yearly". NOTE: to generate weekly, monthly or yearly reports, you need to have at least one daily report schedule if you often clean your DLF store. This is because Lire uses the merging algorithm when it can't find the data in the DLF database and only daily reports are considered in this case.} ); # REFERENCE: lire.xml __( q{Report configuration file to use.} ); # REFERENCE: lire.xml __( q{Report configuration files are text files with a specific syntax designed to describe the type of information displayed in the report and the presentation thereof. Lire provides a typical configuration file for each superservice but you can also create your own, tailored to your needs.} ); # REFERENCE: lire.xml __( q{Report configuration.} ); # REFERENCE: lire.xml __( q{Select the report configuration that should be used for this schedule.} ); # REFERENCE: lire.xml __( q{Select the superservice for this report.} ); # REFERENCE: lire.xml __( q{Lire gathers data by "superservices", which in short are types of "services". This option let you select the type of data that this report job should process, whether it is database, web, email data or any other type available in this list.} ); # REFERENCE: lire.xml __( q{Report Configurations} ); # REFERENCE: lire.xml __( q{List of ReportConfig objects used by this store.} ); # REFERENCE: lire.xml __( q{Report Configuration} ); # REFERENCE: lire.xml __( q{Defines a report that can be used in the report job. A report contains one or more section.} ); # REFERENCE: lire.xml __( q{Report's identifier} ); # REFERENCE: lire.xml __( q{This identifier can be used to refer to this report configuration.} ); # REFERENCE: lire.xml __( q{Report's sections} ); # REFERENCE: lire.xml __( q{List of sections defined in the report.} ); # REFERENCE: lire.xml __( q{Section definition} ); # REFERENCE: lire.xml __( q{Defines a report section.} ); # REFERENCE: lire.xml __( q{Section's filters} ); # REFERENCE: lire.xml __( q{List of filters that will be applied to this section.} ); # REFERENCE: lire.xml __( q{Section's content} ); # REFERENCE: lire.xml __( q{The chart and subreport that will be included in this section.} ); # REFERENCE: lire.xml __( q{Section's Superservice} ); # REFERENCE: lire.xml __( q{The superservices that is used by this section.} ); # REFERENCE: lire.xml __( q{Section's title} ); # REFERENCE: lire.xml __( q{The section's title that will appear in the generated report.} ); # REFERENCE: lire.xml __( q{Report's title} ); # REFERENCE: lire.xml __( q{A title that will appears in the report.} ); # REFERENCE: lire.xml __( q{Path to the sendmail(1) program.} ); # REFERENCE: lire.xml __( q{DlfStreams configuration} ); # REFERENCE: lire.xml __( q{This configuration list contains configuration for each DlfStreams in the store.} ); # REFERENCE: lire.xml __( q{Name of the tai64nlocal(1) program.} ); # REFERENCE: lire.xml __( q{Some log files, particularly those left by programs written by professor D.J. Bernstein, use a timestamping format called tai64n which represents points in time in nanosecond precision using the TAI timebase. This program is required to do the conversion of TAI seconds to UTC seconds. For more information, visit DJB's website. Specifying a full path is optional but recommended. If you're not processing any log files using this format (like qmail or djbdns), you don't have to touch this value: it is ignored by Lire in this case.} ); # REFERENCE: lire.xml __( q{Path to the tar(1) program.} ); # REFERENCE: lire.xml __( q{Path to the unicode.tex file} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: lire.xml __( q{Obsolete} ); # REFERENCE: ct_dist.xml __( q{Distribution curve} ); # REFERENCE: ct_dist.xml __( q{Controls whether or not a bspline curve will be drawn over the plot.} ); # REFERENCE: ct_dist.xml __( q{Variable} ); # REFERENCE: ct_dist.xml __( q{Numerical variable for which the distribution will be plotted for the cases selected by 'case_var'.} ); # REFERENCE: ct_lines.xml __( q{Plot numbers} ); # REFERENCE: ct_lines.xml __( q{Plot the y number beside the points?} ); # REFERENCE: ct_lines.xml __( q{Numerical X Variable} ); # REFERENCE: ct_lines.xml __( q{If you select a numerical variable here, it will be used for the X axis instead of the 'case_var' variable.} ); # REFERENCE: ct_lines.xml __( q{First Y Variable} ); # REFERENCE: ct_lines.xml __( q{Select the variable which represents the Y component of the points.} ); # REFERENCE: ct_lines.xml __( q{Second Y Variable} ); # REFERENCE: ct_lines.xml __( q{Select a second variable to plot.} ); # REFERENCE: ct_lines.xml __( q{Third Y Variable} ); # REFERENCE: ct_lines.xml __( q{Select a third variable to plot.} ); # REFERENCE: ct_lines.xml __( q{Fourth Y Variable} ); # REFERENCE: ct_lines.xml __( q{Select a fourth variable to plot.} ); # REFERENCE: ct_pie.xml __( q{Values Variable} ); # REFERENCE: ct_pie.xml __( q{The subreport's numerical variable that will be used to compute the pie's areas.} ); # REFERENCE: ct_scat.xml __( q{Regression line} ); # REFERENCE: ct_scat.xml __( q{Controls whether or not a regression line will be drawn.} ); # REFERENCE: ct_scat.xml __( q{Label points} ); # REFERENCE: ct_scat.xml __( q{Controls whether or not the points will be labelled.} ); # REFERENCE: ct_scat.xml __( q{X component} ); # REFERENCE: ct_scat.xml __( q{Select the variable which represents the X components of the points.} ); # REFERENCE: ct_scat.xml __( q{Y component} ); # REFERENCE: ct_scat.xml __( q{Select the variable which represents the Y component of the points.} ); # REFERENCE: ct_stack.xml __( q{Areas} ); # REFERENCE: ct_stack.xml __( q{Plot stacked areas instead of bars.} ); # REFERENCE: ct_stack.xml __( q{First Y Variable} ); # REFERENCE: ct_stack.xml __( q{Select the variable which represents the first component of the stack.} ); # REFERENCE: ct_stack.xml __( q{Second Y Variable} ); # REFERENCE: ct_stack.xml __( q{Select a second variable to stack.} ); # REFERENCE: ct_stack.xml __( q{Third Y Variable} ); # REFERENCE: ct_stack.xml __( q{Select a third variable to stack.} ); # REFERENCE: ct_stack.xml __( q{Fourth Y Variable} ); # REFERENCE: ct_stack.xml __( q{Select a fourth variable to stack.} ); # REFERENCE: ct_vbars.xml __( q{Plot numbers} ); # REFERENCE: ct_vbars.xml __( q{Plot the y number above the bars?} ); # REFERENCE: ct_vbars.xml __( q{First Y Variable} ); # REFERENCE: ct_vbars.xml __( q{Select the variable which represents the height of the first bar.} ); # REFERENCE: ct_vbars.xml __( q{Second Y Variable} ); # REFERENCE: ct_vbars.xml __( q{Select optionally a variable which represents the height of a second bar.} ); # REFERENCE: of_html.xml __( q{Obsolete} ); # REFERENCE: of_html.xml __( q{Generate the report on one page} ); # REFERENCE: of_html.xml __( q{If you want your report to be diplayed on one page, enable this option. Otherwise a multiple page document will be generated.} ); # REFERENCE: of_html.xml __( q{Use XHTML 1.0 syntax} ); # REFERENCE: of_html.xml __( q{XHTML is the modern form of HTML. XHTML files are actually XML files with an HTML vocabulary. Since XHTML 1.0 is just a little bit more than HTML 4.01, the result displayed will not change considerably but certain people like to live on the bleeding edge...} ); # REFERENCE: of_txt.xml __( q{Encoding used in the formatted reports.} ); # REFERENCE: of_txt.xml __( q{Use this parameter in the case where you want your reports formatted in a different encoding than the system's default.} ); # REFERENCE: schema:lire_import_stats __( q{DLF Schema for ImportJob and AnalysisJob Statistics} ); # REFERENCE: schema:lire_import_stats __( q{This Dlf schema is used to store ImportJob and AnalysisJob statistics.} ); # REFERENCE: schema:lire_import_stats __( q{Start Time} ); # REFERENCE: schema:lire_import_stats __( q{The time at which the job was started.} ); # REFERENCE: schema:lire_import_stats __( q{Processing Time} ); # REFERENCE: schema:lire_import_stats __( q{The duration of the job.} ); # REFERENCE: schema:lire_import_stats __( q{Job Name} ); # REFERENCE: schema:lire_import_stats __( q{The name of the job.} ); # REFERENCE: schema:lire_import_stats __( q{Job Id} ); # REFERENCE: schema:lire_import_stats __( q{The job id to which the stats relate to. This is the job name plus the timestamp of the start of the job. The job id makes it possible to distinguish between different run of the same scheduled import or analysis job. } ); # REFERENCE: schema:lire_import_stats __( q{Lines Read} ); # REFERENCE: schema:lire_import_stats __( q{Number of log lines processed during that job.} ); # REFERENCE: schema:lire_import_stats __( q{Dlf Created} ); # REFERENCE: schema:lire_import_stats __( q{Number of DLF records created during the job.} ); # REFERENCE: schema:lire_import_stats __( q{Ignored Lines} ); # REFERENCE: schema:lire_import_stats __( q{Number of lines ignored during that ImportJob.} ); # REFERENCE: schema:lire_import_stats __( q{Saved Lines} ); # REFERENCE: schema:lire_import_stats __( q{Number of lines saved for later processing during that ImportJob.} ); # REFERENCE: schema:lire_import_stats __( q{Errors} ); # REFERENCE: schema:lire_import_stats __( q{Number of errors encountered during that job.} ); # REFERENCE: schema:lire_import_log __( q{DLF Schema for ImportJob Logging} ); # REFERENCE: schema:lire_import_log __( q{This Dlf schema is used to store information related to importation and analysis jobs. It is this Dlf stream that will contains the lines that were marked for continuation, that were ignored or that had errors during an importation process. } ); # REFERENCE: schema:lire_import_log __( q{Timestamp} ); # REFERENCE: schema:lire_import_log __( q{The time at which that log line was processed.} ); # REFERENCE: schema:lire_import_log __( q{Job Name} ); # REFERENCE: schema:lire_import_log __( q{The name of the ImportJob to which that log line is related.} ); # REFERENCE: schema:lire_import_log __( q{Job Id} ); # REFERENCE: schema:lire_import_log __( q{The job id in which that line was processed. This is the job name plus the timestamp of the start of the job. } ); # REFERENCE: schema:lire_import_log __( q{Line Type} ); # REFERENCE: schema:lire_import_log __( q{A typecode that can be error for line which resulted in an error, continuation for lines marked for processing at a later time and ignored for lines that were ignored. } ); # REFERENCE: schema:lire_import_log __( q{Line Number} ); # REFERENCE: schema:lire_import_log __( q{The log line number.} ); # REFERENCE: schema:lire_import_log __( q{Log Line} ); # REFERENCE: schema:lire_import_log __( q{The content of the log line.} ); # REFERENCE: schema:lire_import_log __( q{Message} ); # REFERENCE: schema:lire_import_log __( q{An optional message logged by the converter.} );