hcts-hra / ziziphus

10 stars 2 forks source link

Tamboti: Group selection for VRA-group editing #119

Open jodevelops opened 10 years ago

jodevelops commented 10 years ago

Note: THIS IS A COPY OF A TAMBOTI FEATURE REQUEST TICKET: https://github.com/eXist-db/tamboti/issues/22

1. New buttons A sketch for some more options to select and view VRA-Records in tamboti. This is closely linked to the group editing mode for the ziziphus image module, which will be outlined soon (elsewhere, neighbour repository).

The group-edit is only valid when there are NO OTHER worktypes selected in the selection (only VRA)

2. Mixed Media Selections We should think of something like the following to prevent confusion:

"There are items in your collection, that are not VRA-Records. In Ziziphus, only VRA-Records can be edited. Proceed anyway?" With this option one can edit ONLY the VRA-Records from a selection and proceed to Ziziphus anyway, when the selection contains "mixed media", as there will be search results with different work-types.

3. "My List" Probably "My List" should not be (mis-?)used for this selection, although there are TWO selection options at the moment, and I believe, that one should be able to preselect within "My List" and proceed to the editing from there, too.

29-10-2013 12-49-31-copy

jensopetersen commented 10 years ago

Hi,

I will look at this when group editing is implemented in Z.

Having a vertical line of check boxes in the hitlist view will not work well: it is only relvant to VRA records and the hitlist will contain records belonging to different formats. Having an empty box here with other formats will look strange.

What is group editing anyway?

There is also a Grid option, in addition to Gallery. What is to be done with that?

Jens

On 29 Oct 2013, at 17:17, Johannes Alisch notifications@github.com wrote:

Note: THIS IS A COPY OF A TAMBOTI FEATURE REQUEST TICKET

  1. New buttons A sketch for some more options to select and view VRA-Records in tamboti. This is closely linked to the group editing mode for the ziziphus image module, which will be outlined soon (elsewhere, neighbour repository).

The group-edit is only valid when there are NO OTHER worktypes selected in the selection (only VRA)

  1. Mixed Media Selections We should think of something like the following to prevent confusion:

"There are items in your collection, that are not VRA-Records. In Ziziphus, only VRA-Records can be edited. Proceed anyway?" With this option one can edit ONLY the VRA-Records from a selection and proceed to Ziziphus anyway, when the selection contains "mixed media", as there will be search results with different work-types.

  1. "My List" Probably "My List" should not be (mis-?)used for this selection, although there are TWO selection options at the moment, and I believe, that one should be able to preselect within "My List" and proceed to the editing from there, too.

— Reply to this email directly or view it on GitHub.

jodevelops commented 10 years ago

There is an increased importance of the fact that different data formats require different environments and interface solutions (like group editing for images - or equally important features for bibliographic data).

I am aware of the multiple data formats but at the same time there is no other way than paying some attention to those differences now as they are "feeding back" into tamboti in more and more ways (at least as long as tamboti is seen as the core management tool for all different data formats). Maybe for the films, there will be other requirements, that are not forseeable right now.

At present, we navigate/ search/ browse through tamboti and pick SINGLE VRA Work records (including their related image records), that are being handed over to Ziziphus.

Group editing (editing 1+ data-sets in 1+ work-records within Ziziphus) was THE MAJOR feature request, when it came to handling VRA Metadata in classroom situations and elsewhere. For certain VRA fields, it is an essential part of the metadata editing workflow and also the users' experience we witnessed so far is very telling in that respect.

The new challenge in my view is to find a collaborative strategy for selecting 1+ VRA records in tamboti and handing them over to Ziziphus from Tamboti. We are not planning to integrate a search/ filter/ picking functionality in Ziziphus at the moment, because all this is yet given.

I admit, that the sketch above is a bit "invasive", but at the same time, we would like to take Ziziphus potential further (with multiple records editing, or "group editing" as we call it for now).

My proposition is a filter mechanism that makes sure, that there is an exclusive selection of VRA Records, or even a dialogue in the case of mixed selections, once a user wants to proceed to VRA group editing, like:

"There are records in your selection, that cannot be handled in Ziziphus. Open only VRA-Records of that selection?" [YES] [CANCEL]

Or separate self explanatory buttons: Edit VRA-Records of that particular search result.

Or an inactive button for the respective editing (with a higher learning curve for any user and tooltips).

jensopetersen commented 10 years ago

Yes, but tell me, what is group editing - do the records just get opened in as many tabs? In VRA, there are no groups, as far as I recall.

Jens

On 04 Nov 2013, at 12:23, Johannes Alisch notifications@github.com wrote:

There is an increased importance of the fact that different data formats require different environments and interface solutions (like group editing for images - or equally important features for bibliographic data).

I am aware of the multiple data formats but at the same time there is no other way than paying some attention to those differences now as they are "feeding back" into tamboti in more and more ways (at least as long as tamboti is seen as the core management tool for all different data formats). Maybe for the films, there will be other requirements, that are not forseeable right now.

At present, we navigate/ search/ browse through tamboti and pick SINGLE VRA Work records (including their related image records), that are being handed over to Ziziphus.

Group editing (editing 1+ data-sets in 1+ work-records within Ziziphus) was THE MAJOR feature request, when it came to handling VRA Metadata in classroom situations and elsewhere. For certain VRA fields, it is an essential part of the metadata editing workflow and also the users' experience we witnessed so far is very telling in that respect.

The new challenge in my view is to find a collaborative strategy for selecting 1+ VRA records in tamboti and handing them over to Ziziphus from Tamboti. We are not planning to integrate a search/ filter/ picking functionality in Ziziphus at the moment, because all this is yet given.

I admit, that the sketch above is a bit "invasive", but at the same time, we would like to take Ziziphus potential further (with multiple records editing, or "group editing" as we call it for now).

My proposition is a filter mechanism that makes sure, that there is an exclusive selection of VRA Records, or even a dialogue in the case of mixed selections, once a user wants to proceed to VRA group editing, like:

"There are records in your selection, that cannot be handled in Ziziphus. Open only VRA-Records of that selection?" [YES] [CANCEL]

Or separate self explanatory buttons: Edit VRA-Records of that particular search result.

Or an inactive button for the respective editing (with a higher learning curve for any user and tooltips).

— Reply to this email directly or view it on GitHub.

jensopetersen commented 10 years ago

I could understand if there was a way to edit all work records belonging to a collection and all image records belonging to a work record (obviously with some limits of their number), but I think the logic behind this should be inside Z, not T.

Are you not neglecting to create collection records in e.g. Ethnografische_Fotografie?

Jens

On 04 Nov 2013, at 13:24, Jens Østergaard Petersen oesterg@gmail.com wrote:

Yes, but tell me, what is group editing - do the records just get opened in as many tabs? In VRA, there are no groups, as far as I recall.

Jens

On 04 Nov 2013, at 12:23, Johannes Alisch notifications@github.com wrote:

There is an increased importance of the fact that different data formats require different environments and interface solutions (like group editing for images - or equally important features for bibliographic data).

I am aware of the multiple data formats but at the same time there is no other way than paying some attention to those differences now as they are "feeding back" into tamboti in more and more ways (at least as long as tamboti is seen as the core management tool for all different data formats). Maybe for the films, there will be other requirements, that are not forseeable right now.

At present, we navigate/ search/ browse through tamboti and pick SINGLE VRA Work records (including their related image records), that are being handed over to Ziziphus.

Group editing (editing 1+ data-sets in 1+ work-records within Ziziphus) was THE MAJOR feature request, when it came to handling VRA Metadata in classroom situations and elsewhere. For certain VRA fields, it is an essential part of the metadata editing workflow and also the users' experience we witnessed so far is very telling in that respect.

The new challenge in my view is to find a collaborative strategy for selecting 1+ VRA records in tamboti and handing them over to Ziziphus from Tamboti. We are not planning to integrate a search/ filter/ picking functionality in Ziziphus at the moment, because all this is yet given.

I admit, that the sketch above is a bit "invasive", but at the same time, we would like to take Ziziphus potential further (with multiple records editing, or "group editing" as we call it for now).

My proposition is a filter mechanism that makes sure, that there is an exclusive selection of VRA Records, or even a dialogue in the case of mixed selections, once a user wants to proceed to VRA group editing, like:

"There are records in your selection, that cannot be handled in Ziziphus. Open only VRA-Records of that selection?" [YES] [CANCEL]

Or separate self explanatory buttons: Edit VRA-Records of that particular search result.

Or an inactive button for the respective editing (with a higher learning curve for any user and tooltips).

— Reply to this email directly or view it on GitHub.

jodevelops commented 10 years ago

"do the records just get opened in as many tabs?"

No. Group editing will be a specific solution within Ziziphus to edit more than one VRA Record at once, but based on a specific selection, even maybe from more than one collection. Instead of only one VRA UUID, tamboti should be able to hand over more than one VRA UUIDs (WORK) to Ziziphus and Ziziphus then reacts to that by switching into "Group editing mode" (which we are trying to developping at the present moment). A group starts at 2 VRA Records, 12, 23, 37, or even 199 or whatever makes sense to a user to put into one group for "sync" editing).

jensopetersen commented 10 years ago

OK. I would suggest that we wait until "Group editing mode" works in Z and has proven useful, before we start making fairly deep changes to T.

On 11 Nov 2013, at 12:35, Johannes Alisch notifications@github.com wrote:

"do the records just get opened in as many tabs?"

No. Group editing will be a specific solution within Ziziphus to edit more than one VRA Record at once, but based on a specific selection, even maybe from more than one collection. Instead of only one VRA UUID, tamboti should be able to hand over more than one VRA UUIDs (WORK) to Ziziphus and Ziziphus then reacts to that by switching into "Group editing mode" (which we are trying to developping at the present moment). A group starts at 2 VRA Records, 12, 23, 37, or even 199 or whatever makes sense to a user to put into one group for "sync" editing).

— Reply to this email directly or view it on GitHub.

MatthiasArnold commented 10 years ago

I'd suggest we have a meeting once Jens is back to HD. "Group" or "batch" editing is essential when you are working with (metadata of) images, or annotating them. We need to come to a common understanding of the things we are (and have been) talking about. This will also help deciding where the functionality should be implemented.

jensopetersen commented 10 years ago

I am all for implementing this, and it need not be difficult, but I need some answers. There is no reason why these answers cannot be given in the Ziziphus Issues.

What is the reason why use of My List is ruled out for this purpose? This would allow user to select records that are not in the same found set. As far as I can see, the workflow 1) collect records > 2) add or remove or selct records from this collection > 3) edit this collection as group in Z, is very sound. Finding all records one wishes to group edit in the same found set can be difficult, I imagine.

What I see as problematic with the proposal as it is is that it 1) cuts across several divisions in the Tamboti app structure (session.xql and application.xql) and 2) sets up three global interface elements that are only relevant to VRA records. The first makes it necessary to recode central parts of Tamboti and the second will be confusing to non-VRA users (and confusing to all users when different records formats are contained in the displayed part of the hit list). Please explain why such "invasive" methods are called for?

Using My List (or a similar list) would make group editing much-much easier.

Please explain what are the salient features of group editing. Are any fields common to a group, i.e. is it established as some kind of collection? What exactly is being synced?

Why are no collection records being created for VRA collections (as I would call them) in e.g. Ethnografische_Fotografie?

jensopetersen commented 10 years ago

The form of a Tamboti call to Ziziphus to edit one record is

http://kjc-ws2.kjc.uni-heidelberg.de:8650/exist/apps/ziziphus/record.html?id=w_c57474ab-17ac-50ee-960f-b2d2f36edc0e&workdir=/db/resources/commons/Priya_Paul_Collection/&imagepath=/db/resources/commons/Priya_Paul_Collection/VRA_images/i_8d5ef478-bb12-5ee2-a1f1-f58b6c443e40.xml

What is the form of a call for group editing?