RELATIVITY PROCESSING EXAM/10
COMPLETE Q’S AND A’S
Can file names be appended after discovery? - -There's currently not a way
to append a file name after discovery but prior to publishing.
-Can images be reprocessed if they have errors? - -As long as the set hasn't
been published, if the image reports an error, you can retry the image and/or
make corrections to the native and then retry the error.
-Does Relativity allow the use of a custom NIST? - -No, There's no official
support for a custom NIST list.
-How do you fix an error after a document is published? - -retry the file
again.
-How does processing work with errors? - -If you publish a processing set,
even documents that have an error associated with them will get a record
entered in the Document object/tab, with the Control Number field populated
at the very least, even if Relativity was unable to determine anything else
about the document. In other words, just because a document has an error
during processing doesn't mean that it won't be displayed in the Document
list with a control number when you publish the processing set. The only way
this doesn't happen is if the error occurs during ingestion and either
Relativity is unable to extract the document from a container or the source
media is corrupt.
-How does Relativity handle calendar metadata? - -The processing engine
captures all the dates of calendar items. If there is not a field for it in
Relativity, this data will end up in the "OtherProps" field.
-How does Relativity process audio and video? - -Audio and video files are
identified, but no metadata (other than basic metadata) or text is extracted
from them. They will be marked as unprocessable.
-How does processing handle regional setting changes? - -Discovery is
performed on all natives in UTC. Processing uses the timezone as defined in
the processing set settings to convert metadata dates and times into the
selected timezone. For Daylight Savings, there is a table called
dbo.TimeZone in the Invariant database that is used to account for Daylight
Savings Time on a year-by-year basis. This way, we always use the accurate
DST rule for the given year.
COMPLETE Q’S AND A’S
Can file names be appended after discovery? - -There's currently not a way
to append a file name after discovery but prior to publishing.
-Can images be reprocessed if they have errors? - -As long as the set hasn't
been published, if the image reports an error, you can retry the image and/or
make corrections to the native and then retry the error.
-Does Relativity allow the use of a custom NIST? - -No, There's no official
support for a custom NIST list.
-How do you fix an error after a document is published? - -retry the file
again.
-How does processing work with errors? - -If you publish a processing set,
even documents that have an error associated with them will get a record
entered in the Document object/tab, with the Control Number field populated
at the very least, even if Relativity was unable to determine anything else
about the document. In other words, just because a document has an error
during processing doesn't mean that it won't be displayed in the Document
list with a control number when you publish the processing set. The only way
this doesn't happen is if the error occurs during ingestion and either
Relativity is unable to extract the document from a container or the source
media is corrupt.
-How does Relativity handle calendar metadata? - -The processing engine
captures all the dates of calendar items. If there is not a field for it in
Relativity, this data will end up in the "OtherProps" field.
-How does Relativity process audio and video? - -Audio and video files are
identified, but no metadata (other than basic metadata) or text is extracted
from them. They will be marked as unprocessable.
-How does processing handle regional setting changes? - -Discovery is
performed on all natives in UTC. Processing uses the timezone as defined in
the processing set settings to convert metadata dates and times into the
selected timezone. For Daylight Savings, there is a table called
dbo.TimeZone in the Invariant database that is used to account for Daylight
Savings Time on a year-by-year basis. This way, we always use the accurate
DST rule for the given year.
