Custom Query (44 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:

Results (28 - 30 of 44)

← 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 →
Ticket Resolution Summary Owner Reporter
#18 fixed Development of more base views/Browsing Views rmunsky, jurzua Robert Munsky
Description
  • Here we implement the views defined by the screenbook discussions.
  • We will implement editing and browsing views. There is no real difference between them because a user should always be able to edit data directly when he/she sees it if he has got the permission to do so.
  • Parts of the browsing faccility are already done in MS 1.We will define a set of views for traversing through the entered date.
  • We could begin with a list of all objects (author, manuscript and so on) and you can click on them. After doing that you can see all the attributes and relations. When following a relations you see the attached structure.
  • Data traversal shall be done via comboboxes or direct links and inline page elements withot reloading the whole page. Perfectly the user shall not leave the page at all. Inline editors and suggestive fields (ajax) shall give a fluent user interface expireence.
  • Target of that milestone is to give the system a look and feel that it is intuitive to use and does not require long get-to-know-how-it-works time.
  • Robert will prepare some basic concepts such as inline editors and suggestive fields.
  • Jorge will do the rest and the majority of the work

This views define only views which are not part of the data entry views which can be used for simple . If we have solved the on-the-fly character normalization this could work for all kinds of characters.Beginning of query definitionviews and result. search with filters and creation of new level of resultset. drill down based on filter criteria. You will be offerd the attributes of the basket to drill down further.

Additional Requirements from Jamil to query in the browsing views: 1) 2.5--Regarding searches/queries: I would like to make a distinction between queries used by the data editors and queries that will be used by a general user. For the time being (i.e. for Milestone 2), I think we can limit development to the queries used by the data editors. We will leave general queries to Milestone 3.

2) 2.5--What we need are the following query fields for the data entry forms:

  1. For MS
    1. TEXT-title [both pull down and text entry in both Arabic and Latin script]
    2. PERSON-name (role=author) [both pull down and text entry in both Arabic and Latin script]
    3. MS-CITY-city [pull down]
    4. LIBRARY-library [pull down]
    5. COLLECTION-collection [pull down]
    6. ms-num [text entry]
  2. For TEXT
    1. TEXT-title [both pull down and text entry]
    2. PERSON-name (role=author) [both pull down and text entry in both Arabic and Latin script]
    3. PASSAGES
      1. incipits
      2. ends [=explicit]
  3. For PERSON
    1. name [both pull down and text entry in both Arabic and Latin script]
    2. role [pull down]
    3. ALIAS-name [[both pull down and text entry in both Arabic and Latin script]
  4. For ALIAS
    1. PERSON-name [both pull down and text entry in both Arabic and Latin script]
    2. role [pull down]
    3. AIAS-name [both pull down and text entry in both Arabic and Latin script]
  5. For PASSAGE
    1. TEXT-title [both pull down and text entry in both Arabic and Latin script]
    2. PERSON-name (role=author) [both pull down and text entry in both Arabic and Latin script]
#17 fixed 2.1.b - Screen Discussion - Part II rmunsky, jragep, rcasties Robert Munsky
Description
#16 fixed 2.1.a - Screen Discussion - Part I Robert Munsky Robert Munsky
Description
  • planned time: 1 day Dirk, R. C. and R. M. all together at MPI
← 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 →
Note: See TracQuery for help on using queries.