Job "add time" issue

An issue was reported whereby when a job was manually added it was displaying the job add time according to server time.  This has been changed, and account time is now being used.

Upload Report issue

An issue was reported whereby a coding error appeared if an uploader requested an upload receipt after the expiry of an upload session.  This has been rectified.

Primitive Uploader

An issue was reported whereby on completion of upload using the Primitive Uploader, the completion text was not displaying.  This has been fixed.

Adding new clients

An issue was reported whereby when an unrecognised client uploaded and the administrator added them as a new client, some of their information was saving in their client profile but not in jobs they had already added.  This has been fixed.

Upload tools

On the upload tools page, ScribeManager users may now opt to display only some of the upload tools if they wish.  The Standard Uploader tool will no longer be displayed for all users except by special request.

Alteration in default email wording

In the default transcript email to clients, "Minutes claimed" has been changed to "Audio minutes" on request.

Jobs List page search box

Some administrators were not aware that the Enter key should not be pressed after entering a search term on the Jobs List page.  The default text in the search box has been altered to clarify this.

Names of uploading files displayed

The names of files on the Jobs List page are now displayed in all situations, even before they are fully uploaded and converted. 

Upload report issue

An issue was reported whereby a coding error was displayed when an administrator requested an upload report after adding a file.  Since upload reports are non-essential for administrators, that feature has been disabled.

Optional hiding of typist records

A request was received to programme the option of hiding transcription records from typists.  This has now been complied with.

Manuals updated

Updated manuals have now been published and are available for download at:
http://www.scribemanager.com/manuals.html

URL adder

It is now possible to add URLs to ScribeManager instead of sound files.  This means the file is hosted on a third-party site such as YouSendIt, rather than on ScribeManager.  To add a URL, create the job, then go to the Job Edit page, then go to "To add a sound file, click here". 

Files added in this way are not automatically converted or timed.

Billing system altered

ScribeManager's billing system has of today been changed from "per MB" to "per line".  This brings ScribeManager into line with medical transcription workflow systems, allows for greater predictability of costs, and enables a wider range of features.  The standard rate is US $0.0015 per line.  Invoicing will now take place at month-end, not on a "real-time" basis.

To view full revised costings, go to http://www.scribemanager.com/about.html and select the profile that describes you, then click "here" to see costings.

Upload receipt

A request was received for the upload receipt link to be made more prominent.  This has been complied with.

Apostrophe issue corrected

An issue was reported where apostrophes in a transcriber's name were conflicting with code on the Edit Job page.  This has been corrected.

External file transfer systems integrated

ScribeManager clients can now accept file uploads not just via ScribeManager's built-in upload tools but also via any file transfer service that delivers file downloads via a URL, such as YouSendIt. 

Email address required on upload

It was previously possible for a client to upload files without identifying themselves with an email address.  This has been altered and an email address is now mandatory.

Cookies issue

A issue was reported in which, in rare circumstances, an admin clicked a client's magnifying glass to log in as the client, and received a coding error.  This was being caused by a failure of some browser configurations to store cookies.  A message was added to ScribeManager advising the user simply to close down the browser window containing the error and reopen it.  Doing that should store the cookie, and the page will now be visible.