{3} All Tickets by Milestone (21 matches)

This report shows how to color results by priority, while grouping results by milestone.

Last modification time, description and reporter are included as hidden fields for useful RSS export.

2 MS Ressource Plan Release (1 match)

Ticket Summary Component Version Type Owner Status Created Description
#29 Project Resource Plan ISMI model task new Aug 26, 2008
#TitleDuration in Days RM JU
MS 2.0
27Access Database Merge07done
30Change of the openmind data structure to reflect the changes mentioned by Jamil05done
MS 2.1
162.1.a - Screen Discussion - Part I10done
172.1.b - Screen Discussion - Part II10done
18Development of more base views/Browsing Views515done
22Plugin for library/organisation/country dependend normalisations12x
24Discussion about queriing the entered data01done
28Calendar Converter02done
37Secure Transaction03done
MS 2.2
19Definition Structure Editor28x
20Collision Detection02x
35possibility to add relations00,5done
36actualize the database00,5done
52configurable entity/definition label03done
MS 2.3
14UI connected to Flash (optional, duration subject to requirements)--x
21Visualization of relations05x

Changes between 20.Dec 2008 and after Meeting on 10.01.2009 Berlin

JorgeMinor Fixes for search, ordering, import etc, Ticket#45 appr. 5 days
RobertMinor Changes, Ticket#45, Ticket#46, ticket review, performance tests/optimization, meetings2 says

3.0 Metadata View/Editing Release (7 matches)

Ticket Summary Component Version Type Owner Status Created Description
#14 UI connected to Flash ISMI model task Robert Munsky, Robert Casties, jragep, sragep new Jun 9, 2008

It should be discussed, how the user interface can be connected to flash.

#19 DefinitionStructureEditor ISMI model enhancement new Jul 15, 2008
  • Build a view to create/change new definitions. the definitios shall be stored in a persistent way. So you are able to enhance your data domain model by your self without the need for calling a developer.
  • We have to find a way to ensure that when a definition changes no data gets lost or the data will be transformed/copied or the user will be asked to delete them. In addition to that you can define which role the people need to have to add or approve data.
  • There will be an optional flag at each structure which enables a simple workflow with approval from people with a certain role. you will also need to have a certain role (defined in the definition) to the forms for the complex structures (definitions) will be visible automaticaly. All you have to define is an index when you define the structure. New structures will appear in a list of forms you can use to add data.
  • More complex workflows should be defined for the second part of the project. I could think about adding a rule or business process engine for easy definition of workflows.
  • Comments from RC: "When dealing with changes to the object definitions we should identify easy to handle cases to implement first like adding a new attribute which doesn't have to impact other objects and transactions immediately. I second that we should implement a simple permission and workflow model (editor/admin, data-entry, read-only) in the first milestone and think about more complex workflows later.
  • "The permissions shall be used in the browsing views to change access and read/write ability.
#20 Collision detection ISMI model defect new Jul 15, 2008
  • To test the relation changes you will be work on a user sandbox repo version. You can overwrite the sandbox at any time. The changes of the meta structure shall be traced and replayed in the original datastore.Renaming of relations shall be reflected by some business logic. All releations with the same name shall be renamed. Attributes are treated the same way.You should be able to rename relations for a single object class.Deleted relations shall be treated as a flag on relations and shall only be shown on request.cron job backup of the whole datastore should be build in. Collisioni detection should be built in. Merge or sync of repository versoins shall be discussed.A discussion about further meta data changes shall take place later. Maybe the on the fly generation of new definitions based on filters and other criteria should be built in (OWL DL) Split this taks into creation and modifiing of meta data structure
#21 Visualization of relations ISMI model defect new Jul 15, 2008
  • In MS 2 we visualize the relation/meta structure of the definitions (graph viz).
#22 Plugin for library/organisation/country dependend normalisations ISMI model defect jurzua new Jul 15, 2008
  • There should be a way to develop plugins for diffent methods of normalization of arabic letters to latin.
  • The user should click on a flag at the top of the page to change the transcript of the arabic letters.
  • With that we could enhance the usability of the webapp for users from different countries.
  • Jamil has build some transcript algo in VBA.
  • The library of congress uses a special alogo, this could also be a base version for the first implemented plugin.
  • Technical: It is enough when the transcript plugins are build as grails app plugins. There wont be too much of them and they will not have to be able to be plugged in/out during runtime.

Additional Comments from Jamil to the transliteration problem:

3) 2.6—TRANSLITERATION PROBLEMS

  1. all data editors will have a Unicode font, say Arial Unicode MS or equivalent so there should not be a problem; extended Unicode fonts including Arabic script and transliteration characters are freely available online
  2. most important will be the ability to enter query data without transliteration and the search will include characters with diacritical markings: e.g. a search for <u> will return <ü>, <ū>, etc
  3. alphabetizing in text/combo boxes, etc. should ignore
    1. <al->
    2. <>, <’> <‘> <ʿ> <ʾ> (Arabic ayn and hamza)
    3. brackets <[ ]>
    4. others as needed
  4. create macros that convert Arabic script into various Latin transliterated script
#33 Openmind Performance repository layer defect new Oct 1, 2008

Always when Openmind is active, it load all the data (for the case of a database as access, only the needing information have to be loading). A solution to the performance is not approachable for the 2nd milestone. Openmind works extremely slow with a datastore bigger as 2MB. This problem should be discussed!

#42 implement a default alphabetical order ISMI model defect Robert Munsky assigned Dec 2, 2008

Alphabetical order – none is alphabetical, there should be implemented a default order which ignores the articles (in Arabic language a lot of words starts with “al” they should be ignored!). This shall be done after inserting the source code changes from Jorge. Robert will check it.

4.1 Advanced View Features Release (3 matches)

Ticket Summary Component Version Type Owner Status Created Description
#23 Present a graph for the relations and present direct editing there ISMI model defect new Jul 15, 2008
  • We could develop a graphical Graph editing view. There might be a problem when editing already used relations.
  • Image maps can be produced on the fly.
  • Popups can be used as editor forms.
  • With that the user can fly over the data structure and can edit directly on the structure instead of editing in lists of entities.
  • This could lead to an enormous increase of usability.
#25 Multi server problem ISMI model defect new Jul 15, 2008

the first version of the system can only run on one server instance that should be good for a large number of users and shall not lead to memory or runtime problems but we should think about a larger amount of users, multiple data entering projects on one machine. The we might need a clustered environment. Esp. queries could lead to much traffic or machine load

#26 more reliable data storage, faster storage ISMI model defect new Jul 15, 2008
  • we should also try to store the data into a database as mentioned in one of my first emails. We should concentrate on faster and more reliable storage than the currently used file based storage.
  • To get the new user interface running this is not important but fail over save and transactional storage will be a key issue in a productive system and we should focus on that in that milestone. I recommend trying to store the data via an object/relational mapper into a relational database. with that we get transactional security, backups and redo facilities

bugs found by Katja Release (10 matches)

Ticket Summary Component Version Type Owner Status Created Description
#53 go-back-function switchs to login page ISMI model task Jurzua new Jan 23, 2009

If I click on edit in a "show-all-entities"-list ISMI sends me back to the login-page. It would be better if it switchs back to the list.

#54 View of different definitions ISMI model defect Jurzua new Jan 23, 2009

If i open the list of all institutes, and want to open another defintion the page doesn't show the definition i changed to. it still shows the list of the institues, but the menu gives me the possibility to show me all entities of another definition.

#55 Loading of page takes a long time ISMI model defect Jurzua new Jan 23, 2009

If i click on new entity or edit entity it takes 30 seconds to load the page.

#57 add relation - description of relation is placed in different manner ISMI model defect Jurzua new Jan 23, 2009

In different browsers it looks different if i want to add a new relation. If i click on the button add relation, the combo box is placed on the right side (very right) of the page (Opera, Firefox) or it is under the description field of the new relation (IE).

For better understanding take a look at the screenshot

#58 in edit mode it should be shown which dataset will be edited ISMI model defect Jurzua new Jan 23, 2009

If i click on "edit" it should be shown which dataset would be edited. that means, it should be shown the name of the dataset and the kind of definition. furthermore: if i want to interrupt editing, and just want to go back to the list, there should be a button "back to list", which allows me to go back without any changes. a question like "are you sure, that you don't want to save the changes which were already made?" should be asked.

#59 open list in new window- error ISMI model defect Jurzua new Jan 23, 2009

if i would like to open a list in another window a error message appears. (screenshot)

#61 view of related entities ISMI model enhancement Jurzua new Jan 23, 2009

maybe it should be discussed, if it is necessary or nice-to-have:

in the list of all entities i am able to see detailed information (with all related entities) about every entity. maybe it is a good feature, if it would be possible to click on the related entity and switch to the entity in their own list. for example: I am in the list "institutes" and see all of them. i click on one institute and can see that a person is related to my institute. than it would be nice, if i am able to click on that person, and will be guided to the persons list, where i can edit that person or delete.

#62 next / previous page on the top AND the bottom of a page ISMI model defect Jurzua new Jan 23, 2009

on the top of every list I am able to go to the next or the previous (list-)page. This should be also possible at the end of my page.

(sometimes the lists are very long, and it would be great to have the posibbility to go to the next page easily from the end of the page as well as from the top of the page.)

#63 time-out-problem ISMI model defect Jurzua new Jan 23, 2009

after a while there is a time-out without any warning. you just realize that there was a time-out because of the disfunctionaliy of some feature (e.g. if i want to see a list, i'm not able to delete or add new entities)

#64 Duplicate entries after save action ISMI model defect new Jan 29, 2009
  • create a person or another entity
  • press save more than once (a doubleclick can easy happens)
  • now wait a little bit and then search this entity
  • there are now several entries in the database

This is especially problematical if this entity shall later related to other entities.

Note: See TracReports for help on using and creating reports.