We are working with a client the Ministry of Justice (MoJ) in New Zealand to provide them a solution to perform core transcription services for the District Court, higher courts (High Court, Supreme Court), and specialist courts and tribunals of New Zealand.
The transcripts their court reporters produce must follow a strict naming convention. The transcribing will be completed using ROS. The naming of these documents need to follow the conventions as they will be accessed throughout the process by members of their team as well as external parties such as Judges and Judicial Counsel. The limit of 75 characters for FLNM (Filename) is restricting and does not allow them to use these conventions. Thanks, Paulina
The long file name is also a problem that we had to build a custom solution for to prevent capture items from aborting when attachment file names are longer than 75 characters. This was particular tricky because in order for the attachment to successfully archive to the AFT server; the file extension is required and it is often outside of the first 75 characters. Being able to index more than 75 characters would definitely be beneficial.
Chorus is unable to store email addresses of more than 75 characters.
Email standards allow for up to 320 characters in email addresses and we cannot control the addresses used by our clients/CMOs so we need Chorus to store email addresses of the full 320 characters. This is currently leading to email uploads failing silently and requires urgent remediation.
Please explain what you mean by a client's "reference field"
Both Processor Workspace and ROS have recent enhancements automatically handle the filename lob dataname field length truncation when the value is > 75
Please elaborate on steps to recreate the circumstances where a subject line variable >99 is being used where Chorus stops responding (is this inbound from capture input message or outbound in communications) where in a service does it fail does it abort? version? release? related ticket open?)
Note that Communications outbound support of email and subject is 255 characters today.
A1. There is a field on Chorus customized for us, input to this field is limited to 75 char.
A2. If that's right then could you please confirm with your colleagues, Tom Wynne, Leslie Greenan so they could incorporate in to the Chorus that we are using?
A3. Tom Wynne and his team are working for a solution for this as well, they can show you as well. CPC INC1382880, for your easy reference.
2. The Processor workspace change was delivered so it does not fail when the filename is greater than 75. Note that the file name is a reference field only and is not used in any way as part of the retrieve and view source functionality.
3. In the automation service for the capture product, most clients use an expression to truncate the length of that field from the message so that it can be set into the LOB field without error.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
