|
Even older news
|
|
2008-12-30 The 547 revision provides the following functionality: ● the Thematic Domain Groups (TDGs) and their profiles have been synchronized with the new TDGs and activities list ● the Data Category editor is now operational, although the part to edit conceptual domains and linguistic sections has not been implemented yet ● a Data Category specification can now be checked against a set of rules derived from the current draft of ISO 12620.2 ● interface elements have been checked on proper capitalization ● the internal set of data categories related to the DCR data model has been updated and extended leading to a better rendering of a Data Category specification Note: This update includes several updates of the database schema and contents. To facilitate a smooth propagation of these to the production server the database will be replaced, which means that user accounts and DCSs created since the beginning of December will be lost. Note: Firefox shows from time to time its default login dialog.
2008-12-8 On January 7 and 8, 2009 the first DCR Board meeting, followed by an ISOcat tutorial/workshop, will take place in Tilburg, The Netherlands. See the DCR Board meeting and ISOcat workshop website for further information about this event.
2008-12-1 The 485 revision provides the following functionality: ● the search functionality has been extended, although this isn’t yet available in the UI ● the DC editor now validates the identifier, and won’t allow you to save a duplicate; when there aren’t private duplicates but public ones it also pops up a warning ● the database has been updated with the state of SYNTAX on 17 November 2008; unfortunately this means that user accounts and DCSs only available on ISOcat are lost ● fixed a basket bug ● added scope and owner information to the DC viewer ● by default sort a profile/DCS on the name ● suppress profile value domains of non-context profiles ● reset paging model when switching to a flat DCS view ● added a context menu (activated with a click on the right mouse button) to hide/show columns in the DCS viewer; the identifier column has been added as a by default hidden column
2008-11-15 The 442 revision provides the following functionality: ● the ISOcat software has now a SourceForge project ● more “loading …” info ● reset scrollbars when the next DC is loaded ● adapted the DCIF schema to support different levels of granularity ● added support for a ‘domain oriented’ DCIF dump ● added support for nested DCSs ● full support for rendering hierarchies in the DCS viewer ● suppress references to simple DCs which aren’t part of the selected profile/DCS
2008-11-5 The 430 revision provides the following functionality: ● more support for nested profiles ● added initial help system ● reworked the (public) REST interface ● added support for a shallow DCIF dump (support in the export dialog is pending) ● added thematic views intermediate level ● it’s now possible to drag multiple DCs to the basket ● started adding support for rendering DC hierarchies in the DCS viewer The revision also fixes some known issues
2008-10-9 The 401 revision provides the following functionality: ● colorings of statuses in the DCS viewer ● more of data model is covered by the DC editor; however, it’s not yet possible to save the changes made
2008-8-11 The 354 revision provides the following functionality: ● a RDF(S) export format for Data Category Selections
2008-8-9 The 343 revision provides the following functionality: ● expert users can now preview the DC editor form ● the DC and DCS views can now be detached, i.e. opened in an window, in the Explorer and Tabbook views ● My Workspace and the TDG nodes in the workspace viewer can now be selected, which shows information for the user or about the thematic domain group
2008-8-4 The 320 revision provides the following functionality: ● the Syntax data has been (partially) converted into the revised data model as described in the upcoming ISO 12620 ● the interface has been adapted to also support this revised data model ● the revised DCIF is supported ● many more (minor) changes to the interface
The following functionality is (temporarily) dysfunctional: ● the GMT export format, which may be resurrected but then based on the revised data model ● the Syntax RPC interface depends on the GMT export and thus is also dysfunctional at the moment; the RPC interface will also be resurrected but only the procedure prototypes will be backward compatible, results will conform to the revised data model
2008-6-27 The 263 revision fixes the following functionality: ● fixed the email validation regular expression ● the DCR data model DCS is now properly cached, leading to much improved DC rendering performance
The following additional changes were made to this page: ● the LREC paper has been published ● the planning has been updated ● added a section containing information on ISO 12620
2008-5-19 The 220 revision fixes the following functionality: ● the known issue 'on resize events the main views are not repainted' has been fixed by explicitly requesting a repaint of the active view ● an export of a DCS will now also respect the (temporary) relax flag
2008-4-17 The 207 revision provides/fixes the following (new) functionality: ● a keyword search function, however the current setup may return DCs which aren't officially accessible by the user ● new rendering of DCs, based on DCs related to the DCR data model ● GMT export for DCSs and the basket ● support for a basic set of procedures from the Syntax RPC interface: 1. getProfiles 2. getDataCategories 3. getDataCategory 4. searchDataCategories the endpoint of this RPC interface is: $site$rpc/syntax, follow this link to get a description of the interface (2012-4-20: removed the obsolete support for the SYNTAX GMT RPC interface) ● almost complete rewrite of the database access layer, leading to improved performance
2008-2-20 The 168 revision provided/fixed the following (new) functionality:: ● user management: 1. new users can register 2. existing users can login 3. existing users can recover their login details 4. existing users can update their user profile ● DCS management: 1. create a new private DCS 2. edit and save a private DCS ● a rudimentary REST API ● the REST API enforces some access control ● various fixes to synchronize the loading of UI components ● front-end code cleanup ● fleshed out more of the back-end modules
|
|
ISO TC 37 Terminology and Other Language and Content Resources |
