Usability of view editing in list view

Usability of view editing in list view

Ralf Hilgenstock -
Erantzun kopurua: 7
Core developers-ren irudia Translators-ren irudia

The database activity has a great potential for more learner centric learning. In lots of discussions teachers told us that the idea is great and they would like to used it but usability is really a mess. Specially the list view editing process is not usable for a normal teacher. To create acceptable results some understanding of HTML is needed that most teacher don't want to use. The text editor often breaks the process.

I've thought for a long time how to simplify this process and I think there is a way we can do it. Lets implement a new simple form for standard view definition. If the user opens the form he sees a table with all data fileds created earlier plus the system fields #'user## et al. He can mark the fields that should be used for the table, a second column shows the order of the fields and the last one is the title as defined when fields are edited. If fields are selected and ordered they can save the changes and the view will be created.

Most teacher accept to use a standard design for the tables and are not interested to change them. Advanced users can click at the link 'advanced' modus to use the traditional way to define the views.

This process could be implemented for all four views: new entry, search, list, and single. Top priority has the list view, because it creates most of the problems.

Please comment aloso at MDL-36152

Eranskina database.png
Puntuazioen batez bestekoa: -
Ralf Hilgenstock(e)ri erantzunda

Re: Usability of view editing in list view

Itamar Tzadok -

Another possible way is to display a table in the template and columns could be added/removed from the editor toolbar, and tags added the standard way from dropdown or by typing.

To illustrate

 

 

Ralf Hilgenstock(e)ri erantzunda

Re: Usability of view editing in list view

Itamar Tzadok -

Another approach, closer to your conception of a simplified form but in a sense more simplified and yet possibly more flexible is a simple text area where instructors can specify each column in a new line.

##author:name##
[[Concept] ]
[[Definition] ]
##edit##
##delete##

The tags can be selected from a dropdown or typed in. This makes it fairly easy to set the order of columns. A further enhancement allows for adding header titles:

##author:name##|My Name
[[Concept] ]|My Concept
[[Definition] ]|My Definition
##edit##
##delete##

In a similar way it could be possible to add a css class to set styles for the cell from the css tab.

irribarrea

Itamar Tzadok(e)ri erantzunda

Re: Usability of view editing in list view

Ralf Hilgenstock -
Core developers-ren irudia Translators-ren irudia

Hi Itamar

our common idea is to go away from the three editor field concept.

The first ideas from you will work with a few database fields only. If a database has 15 or 30 fields the table is to wide to be usable. For typical teachers the handling of tables in the editor is complex and here we can try to replace it by an other process.

The idea of simple text area entries is interestig but teachers have to learn the codes for the fields.

I don't know how much effort the different solutions create to implement. Martin told during our German Moot this year that he like the database very much because lots of scenarios activating students are possible.  So it should make sense to design the processes carefully.

Ralf Hilgenstock(e)ri erantzunda

Re: Usability of view editing in list view

Itamar Tzadok -

I'm inclined to think that nothing would work reasonably with more than a few fields. Consider the possible number of built in tags (e.g. ##edit## ##delete##; see http://docs.moodle.org/23/en/Dataform_Fields#Built-in_patterns for a list of possible tags in the entry level). The more flexibile the platform the more complex the ui. Just like Moodle 2 by comparison to Moodle 1(.9).

It shold be fairly easy to create a form layer as in your sketch above. It could look something like

 

but with more fields (and there already are quite a few built in tags even before adding fields) its usability would decrease.

irribarrea

Itamar Tzadok(e)ri erantzunda

Re: Usability of view editing in list view

Marie Broxholme -

Oh that's a shame, it doesn't feel like it the right tool to use for what I need.  The database seems more suited I think, but it's a shame it doesn't allow you to search to narrow down the records you want to view or just export selected records.  I guess I could do something with excel for staff to easily ditch the records they dont need after it's exported the whole database etc...  Is there a chance the database mobule can be developed more to include a more flexible search facility and the ability to export a selection of records?  Is there a place where I can suggest an enhancement???

Thanks again for all you help. 

Marie