York Project Update
Previously, this document is to encapsulate the outstanding or reported issues with the last update of
M3Online Prototype II. We use this document now to serve as an update for YRDSB for progress on
Prototype V scheduled for June 1, 2012.
MINISIS has been moving far too quickly on the development and now the reverse reengineering to
have the prototype code compatible with IE 8.0 has run into several hiccups. We are using the latest
Jquery, Java Script developments and Python in the Polygon Framework that this browser compatability
is causing more issues than we had hoped but not something unexpected. Remember, this is an online
database not just a web form. There are countless little security things, dynamic data entry, dynamic
processing that goes on without the user necessarily understanding nor needing to know what is under
the hood – so to speak.
The initially complied list of 13 reported issues is presented below. There were 6 issues in the first
report (1 to 6) submitted on February 23, 2012. Then there were 7 more issues reported (7-13) on
February 27, 2012. Most of the issues were reported as: bugs with one as an enhancement. MINISIS Inc
feels many of the issues listed are more enhancements (user changes, perhaps better UX, change in
usage or function) as opposed to the software not working. We have added underneath each issue ID
occurrence, the status of each previous issue as it relates to Prototype V.
ISSUE ID
1
YRDSB:
“urgent”
MINC: MINISIS is mixed on
this issue. In some regards it
is just a option that we
should be able to turn on/off
for a client. However, given
that there is always a save
button in the Save Process
part of the screen (top left
corner) and a save button on
every form at the bottom it is
thought that this really is an
Enhancement Request and
not a necessity for usage.
MINISIS INC RESPONSE
There is a save icon on the left hand corner process section of the form. There is a
save button on the bottom of the screen as well. The auto save feature request
has been added to Prototype IV. It will add at least two (2) seconds to the
presentation of any form after the user has left a page. There was discussion that
a user message could be prompted to tell the user to save. We canvassed other
users and UX personnel and they said the user message is not an ideal solution
either. As MINISIS keeps the record open on the screen anyway, the additional
user message would be more annoying as you would have to move your mouse to
click the message and then click save, so two clicks instead of a single click. If your
displays are correct you will see a save button on the form and there is the save in
upper left hand corner as shown. The user should also see the black box message
indicating if the record was saved.
Status:
Developed. Tested. Waiting to be implemented.
Details:
Save Button has been added to the top of the catalogue tabs.
2
YRDSB:
“bug”
MINC: MINISIS agrees the
right fields should be painted
on the screen. Bug.
This issue will be fixed in the next Prototype IV. The field that is painted on the
screen is the wrong field as there was no authority data until we received the data.
As YRDSB has not fully documented the desire for the location authority field, this
will be updated when we have that information. For now we will ensure that the
field is correctly added to the top of the screen.
Status:
Developed. Tested. Waiting to be implemented. In production.
Details:
The fields have been harmonised and the right field displaying. York will still need to
provide the information for location authority
No. This issue has been addressed. The Accession Number and Title are the two (2)
minimal requirements to save a record in the other M3 version. It is noted that
there may be records on conversion that did not have a number or a test record
but that is the only time an Accession Number cannot be present. MINISIS will add
in a button that the user can click to get the latest or (N+1) sequential number in
Prototype IV. Again, MINISIS has also made the Accession Number mandatory
with the Legal_title (aka Title). The fix in Prototype III.
3
YRDSB:
“bug”
MINC: Addressed.
Status:
Developed. Tested. Waiting to be implemented. In production.
Details:
MINISIS cannot provide the n+1 functionality on demand from validated list. The
Browsers are unable to interpret the exit from the client-server version. So after trying
and expending resources upon this extra idea, we must put it on the wish list.
Otherwise the field is mandatory with legal title
4
MINISIS has added in a duplicate check feature (Note: there may be issues with
existing data, YRDSB will have to check), This fix is in Prototype III.
YRDSB:
“bug”
MINC: Addressed.
Status:
Developed. Tested. Waiting to be implemented. In production.
Details:
Duplicate check has been turned on the accession number. York will have to let
MINISIS know when it encounters an issue with a locked record (any records that have
the same accession number).
5
MINISIS will determine a manner by which to make the java script roll over tool tip
when rolling over the number more specific and present a little more detail on the
object, (eg: object name, location, status for example). MINISIS must determine
what makes sense and discuss options with YRDSB. Simply, we cannot
accommodate this change as it would affect the entire search/query components
of M3_Online. This feature will have to go on the wish list.
YRDSB:
“enhancement”
MINC: Enhancement.
Status:
Developed. Tested. Waiting to be implemented. In production.
Details:
Duplicate check has been turned on. York will have to let MINISIS know when it
encounters an issue with a locked record (any records that have the same accession
number). As an interim fix, we have included the ACCESSION NUMBER and
OBJECT_TITLE fields on the query display.
6
Event is an authority in the desktop version. MINISIS has removed the authority to
make it free text on M3 Online. Event authority may be added in Prototype IV or V
if the YRDSB wishes.
YRDSB:
“bug”
MINC: MINISIS believes it
should be an authority and
function like all other
authorities. It will be
addressed for free if the
YRDSB wishes to change
back.
Status:
Developed. Tested. Waiting to be implemented. In production.
Details:
Again, this will be an enhancement that will eventually go into the default system in the
next release, if YRDSB wishes to have it be an actual authority.
7
YRDSB:
“bug”
MINC: Addressed.
Error: “Could not update” fields in Ownership . This issue has been fixed in
Prototype III. The field was not in the XML file. This has been remedied.
Status:
Developed. Tested. Waiting to be implemented. In production.
Details:
Added the EXCHANGE_METHOD field to the XML script to allow the user to save the
data in that field.
8
The issue was reported that the Provenance tab was void of any fields. This issue
has been fixed in Prototype III and the form is not populating. The XML script was
updated to respect the db structure.
YRDSB:
“bug”
MINC: Addressed.
Status:
Developed. Tested. Waiting to be implemented. In production.
Details:
The PROVENANCE Tab is now displaying the default fields as requested.
9
YRDSB reported that it was unable to add components to a record. issue is still an
issue in IE 8.0.
YRDSB:
“bug”
MINC: Bug.
Status:
Developed. Tested. Waiting to be implemented. In production.
Details:
The Components tab has been updated with three (3) buttons: ADD, EDIT and DELETE.
10
YRDSB:
“bug”
MINC: To be Addressed.
Should do it in Prototype IV.
YRDSB requested to have any field with less than 10 values in a combo box to be
turned to a drop down menuing presentation. As the YRDSB should be advised
again that by doing this change any additional values would have to come back to
MINISIS to implement. Also, note this will again mean York is further from the
generic version. Also, a “NULL” or ‘blank’ value will be added so that if a user does
accidentally click into the field, they can turn the value to null. MINISIS is
concerned that the arbitrary 10 values is not necessarily the best way to tackle this
issue.
Status:
Developed. Tested. Waiting to be implemented. In production.
Details:
Alas, <<null>> has been added to all lists as well, based on the desktop, fields are
consistent with their structure. Small or limited validated pick lists with no or remote
chance of updating terms conatinned inthe list are now combo boxes (drop down) all
others act like authorities.
11
YRDSB:
“bug”
MINC: To be Addressed.
Should do it in Prototype IV.
The field will be turned to numbers if desired. Many of our clients have words like
approximately or currencies and therefore have to be a free text field. As York has
stated it should be numbers only the field definition will be changed. It was also
stated that no punctuation nor dollar signs will be in the data. Note, this will again
mean York is further from the generic version.
12
The java script will be added into Prototype IV to go from 1800 to 2200.
YRDSB:
“bug”
MINC: To be Addressed.
Should do it in Prototype IV.
13
YRDSB:
“bug”
MINC: To be Addressed.
Should do it in Prototype IV.
(end)
YRDSB requested to have any field with less than 10 values in a combo box to be
turned to a drop down menuing presentation. As the YRDSB should be advised
again that by doing this change any additional values would have to come back to
MINISIS to implement. Also, note this will again mean York is further from the
generic version. Also, a “NULL” or ‘blank’ value will be added so that if a user does
accidentally click into the field, they can turn the value to null.
END OF SUMBITTED ISSUES
Mounir Mounir’s questions in a follow up email after reporting of the above issues.
Below are our observations:
1- Non of our 13 reported issues have been addressed in this new version (I am re-attaching the 2 lists of
issues).
2- Some very important worksheets are now empty, with no fields under them (e.g. Media, Research
and Acquisition).
3- Some other worksheets (e.g. Provenance) are now being populated with fields once more, however
are very unstable (cannot link to lookup data, still have validation errors, and cause the whole
application to stop responding until we log out and log in again).
4- Search results are inconsistent, especially when using Internet Explorer (Safari seems to be faster and
brings more consistent search results).
5- Linking information from the various authorities is not working any more (it used to work with the
previous version).
6- The "Help Document" is not the right one and cannot be used as it provides misleading information.
7- Updates are still being done on this version, as worksheets are being changed, and some of the test
cases that once succeeded are now failing our testing (e.g. Event Name under Associations).