Difference between revisions of "JMdictDB Project"

From EDRDG Wiki
Jump to: navigation, search
(Interface from Other Systems)
(Processing Flow)
Line 17: Line 17:
 
* Stuart's [http://edrdg.org/~smg/ information page].
 
* Stuart's [http://edrdg.org/~smg/ information page].
 
==Processing Flow==
 
==Processing Flow==
 +
 +
'''User Creates/Amends an Entry'''
 +
 +
'''Editor Verifies Entry'''
 +
 +
'''Dictionary Distribution'''
 +
 +
Once each day the dictionary database (approved entries only) is converted to an XML file from which the distribution formats (JMdict, EDICT2, EDICT, etc.) are generated. These are placed on the Monash ftp server and into the Monash WWWJDIC server, from which the other WWWJDIC servers will progressively update their files.
 +
 
==Interface from Other Systems==
 
==Interface from Other Systems==
 
WWW servers and web-enabled devices using the JMdict or EDICT2 versions of the dictionary can link directly to edit screens in the JMdictDB system using the Entry Sequence Number in each entry. This is in the <ent_seq> entity in the JMdict version and in the "EntLnnnnnnn" field at the end of each EDICT2 entry. The URL to use is:
 
WWW servers and web-enabled devices using the JMdict or EDICT2 versions of the dictionary can link directly to edit screens in the JMdictDB system using the Entry Sequence Number in each entry. This is in the <ent_seq> entity in the JMdict version and in the "EntLnnnnnnn" field at the end of each EDICT2 entry. The URL to use is:

Revision as of 08:15, 16 July 2010

JMdictDB Database Project

Overview

The JMdictDB online database has been developed to support the maintenance of the JMdict/EDICT, JMNEdict/ENAMDICT and other dictionary files originally compiled by Jim Breen. From May 2010 the JMdict/EDICT file has been maintained using the database, with full public access enabled in July 2010. The database system has been developed by Stuart McGraw.

Access to the database is in several forms:

  • the WWWJDIC servers link directly to the edit screen of the JMdictDB system when a user wishes to add a new entry or amend an existing entry.
  • other servers using the JMdict/EDICT file are encouraged to offer similar links.
  • JMdictDB system's own search/lookup screens. These can look up entries using Japanese words, English words and the entries' sequence numbers. There is a basic search screen and an advanced search screen]

Users will be able to propose new entries and edit existing entries. New entries and amended entries will be held as "pending" until approved by one of the editors working with the project. The user submissions can be viewed using this page.

The contents of the JMdictDB database are released daily as the current JMdict and EDICT dictionary files, and are automatically added to the WWWJDIC dictionary server.

For more information, see:

Processing Flow

User Creates/Amends an Entry

Editor Verifies Entry

Dictionary Distribution

Once each day the dictionary database (approved entries only) is converted to an XML file from which the distribution formats (JMdict, EDICT2, EDICT, etc.) are generated. These are placed on the Monash ftp server and into the Monash WWWJDIC server, from which the other WWWJDIC servers will progressively update their files.

Interface from Other Systems

WWW servers and web-enabled devices using the JMdict or EDICT2 versions of the dictionary can link directly to edit screens in the JMdictDB system using the Entry Sequence Number in each entry. This is in the <ent_seq> entity in the JMdict version and in the "EntLnnnnnnn" field at the end of each EDICT2 entry. The URL to use is:

http://www.edrdg.org/jmdictdb/cgi-bin/edform.py?svc=jmdict&sid=None&q=nnnnnnn where nnnnnnn is the sequence number

Using that URL results in an entry edit screen being loaded with the current contents of the entry.

Complete new entries can be submitted in EDICT2 format. For example, to submit the entry: "何か [なにか] /(exp) something/", the URL to use is:

http://www.edrdg.org/jmdictdb/cgi-bin/edform.py?svc=jmdict&c=1&j=何か.......

The entry must be in UTF-8 coding and the Japanese and space characters must be "URL encoded", e.g. "%E4%BD%95%E3%81%8B%20[%E3%81%AA%E3%81%AB%E3%81%8B]%20/%28exp%29%20something/".