Changes between Version 2 and Version 3 of IsmiWorkflow

Timestamp:

Jun 5, 2008, 10:12:19 AM (16 years ago)

Author:

anonymous

Comment:

--

IsmiWorkflow

@@ -9 +9 @@
  //NB: In the following bold case is used to refer to the abstract object entities in the database//
   - The user interface (swing or web client) should be in the modus "input new manuscript source".
-  - Look whether the author is already present as a **person** object in the database.
+  - Look whether the author is already present as a '''person''' object in the database.
     * A control mechanism should be implemented to minimize the risk of entering one person twice under a different alias. 
-      * For example if one types "Isfahani" or "Iṣfahānī" or "اصفهاني" all **person** objects (and associated aliases) that match (or are very similar) to those strings would be presented as suggestions to the data editor.((For this a "live-search" facility (like "[[http://www.google.com/webhp?complete=1&hl=en|Google Suggest]]") could be useful.)) Each suggestion would also provide minimal biographical info (place and dates) if available, in order to avoid the converse problem of merging two different persons who happen to share the same name.
+      * For example if one types "Isfahani" or "Iṣfahānī" or "اصفهاني" all '''person''' objects (and associated aliases) that match (or are very similar) to those strings would be presented as suggestions to the data editor.((For this a "live-search" facility (like "[[http://www.google.com/webhp?complete=1&hl=en|Google Suggest]]") could be useful.)) Each suggestion would also provide minimal biographical info (place and dates) if available, in order to avoid the converse problem of merging two different persons who happen to share the same name.
 
   - If it is not present, add it (e.g. in a separate window). 
-  - Identify the author by linking to an appropriate **person.**
-  - Same thing (steps 2-4 above) for **text**.
+  - Identify the author by linking to an appropriate '''person'''.
+  - Same thing (steps 2-4 above) for '''text'''.
     * date of composition
     * place of composition
@@ -28 +28 @@
     * explicit
     * information whether the work has been published, translated, studied, with refs to literature db
-  - Same for **library**:
+  - Same for '''library''':
     * name of library
     * city/country
-  - **collection**: 
+  - '''collection''': 
     * name of coll.
-  - **codex**:
-    * //Usually the **codex** will not be present in the db, unless it is a collection of several works.//
+  - '''codex''':
+    * //Usually the '''codex''' will not be present in the db, unless it is a collection of several works.//
     * codex number.
     * number in codex
@@ -89 +89 @@
     * Date/time work began (for data collection)
     * Date/time work ended
-  *  
+  
+