MetaToo 1.6 Release Note

1. New Features

New features of this release:

1. DAS API enlargement: Adding getUserAuthetication to the Web Service API

   This new DAS API method on the webservice interface to MetaToo will allow any UI which knows the users MetaToo identity to query the authentication status in MetaToo of that user (probably at login time on the UI).

   Using this information, unsophisticated logic is needed in order to determine at run time if that user has access any specific MetaToo record (retrieved as part of a search result). Thus, it becomes possible for UI's to make a qualified decission about wheter or not to include a deep link into MetaToo when presenting the record to the user.

   Ticket: #20; done for project: ORBIT

2. DAS API enhancements

   It is now possible to specify a commaseparated list of ID's (rather than just a single ID) when requesting specific records. Also, any external ID's registered back to MetaToo (for records and/or objects) will now also be part of the DAS response even though the record is marked as deleted.

   Tickets: #27, #45;

3. Adding on-record-save code hooks facility

   Any application may hook in perl code which is executed before and after a record is saved.

   For the ORBIT project: A pre-save hook has been contributed to suspend proofreading (i.e. change status) for records with titles enclosed in "[" and "]" as well as to add project-specific fields.

   Tickets: #22; done for project: ORBIT

4. Accepting full DTU campus user identificators (cwis-numbers)

   You can now give login with or without the initial (indicative) 's' or 'v'.

   Tickets: #31; done for project: ORBIT

5. Paging

   Any screen with a list view may be configured to introduce a pager rather than just a prev/next buttom-pair.

   Tickets: #23; done for project: ORBIT

6. Using authorities more broadly

   Introducing authorities to type Hidden and type ViewOnly, and letting DefaultValue have its value chosen from lookup into chosen authority

   Tickets: #63; done for project: ORBIT

7. MetaToo Version

   The MetaToo Core version number is now displayed in the admin menu.

   Tickets: #43

Tickets for additional enhancements with this release: #12, #49,

2. Bug Fixes

Bugs fixed with this release:

1. Mandatory fields on level three locks the object. Ticket: #24.

2. Fixed bug of mandatorieness check. Ticket: #30.

3. No object/@id for some records (problem worked around; not fixed properly). Ticket: #18.

4. Wrong timestamp for copied records. Ticket: #37.

5. Fixed the missing inclusion of namespace fit for some records when exported through other means than through the DAS. Ticket: #51.

6. Bug in xpath interpreter implementation of API method xpath2field. Ticket: #42.

Tickets for additional bugs which are fixed by this release: #34, #35, #41, #46, #48, #50, #71,

3. Others

Changes to MetaToo applications or other code related to MetToo Core:

1. Mail notification

   When adding a new author to a record (either at record birth or later) that author will be scheduled to recieve a mail notification. Mail notifications are handlede in batch by a script. The mail content reside in a (configurable) template.

   Tickets: #21, #32#33; done for project: ORBIT

2. Fixed ORBIT bugs. Ticket: #28, #36.

4. Patches

1.6-2 fixes bugs #41, #76 and #77

1.6-3 fixes bugs: #54, #79, #85, #89 and an unreported bug with double search terms (e.g. as when searching a title). enhancements: account switch list for root and admin, core-version test method for version specific statement and DAS improvements on large databases.

1.6-4 fixes undocumented bugs:

1. XPATH problem with double slash wildcard (//path)

2. DAS problem with excluding xml and sea fields from record attribute list

3. DTU new CAS server which has to be accessed using CAS version 2.0

1.6-5 fixes undocumented bugs:

1. Minor xpath bug in record lookup

2. Added checks to detect configuration error for new CAS module added in 1.6-4

3. Fix to local managers handling of authentication to allow more flexibility in group definition.

1.6-6 fixes bugs and add features: #75, #83, #96 (partial), #104, #107, #108, #109, #111, #114,

• Note: the solving of #83 and #108 changes the encoding of entities in XML so that standard XML entities which were previously not double encoding when entered in a form, will now be encoded. I.E. before typying A & B or A & B in a form both resulted in the same encoding: A & B. Now, while the first remains unchanged, the second will be encoded as A & B.

• Note: extra debuging log messages have been added with the hope of solving #74 in the next patch.

• Note: the partial implementation of #96 is considered experimental and will only be fully supported in 1.8. You may however experiment with it, using textarea_cdata as a field type and using the fit_textarea_upload manual action.