Design decision - what to show for all occurrences of a value in our texts?

[nevenjovanovic]

@arsimr16 , @NinaCengic , @zeljkasalopek , @azugic - guys, there is a design decision with which I need your help. We will have a URL showing all occurrences for a value - for example, all x mentions of the place y in our corpus. The occurrences are first shown as a number, let's say 7. The number is a link, and when we follow the link, we see the list of segments where the place is mentioned (a, b, c... all seven of them). The question is: what else to show, beside the CITE URN for places a, b, c... and the CTS URN for the segment? What would be useful? Once we have the CITE URN for the segment, we have access to everything, to all notes linked to the URN - what would you like, what would you need to see? The context, the periods, the word forms, the morphology, the lemmata, the standard place names...? Ideas are welcome!

[arsimr16]

I think lemmata and context would be useful.

~Alex

On Wed, Dec 7, 2016 at 5:16 PM, Neven Jovanović notifications@github.com wrote:

@arsimr16 https://github.com/arsimr16 , @NinaCengic https://github.com/NinaCengic , @zeljkasalopek https://github.com/zeljkasalopek , @azugic https://github.com/azugic

• guys, there is a design decision with which I need your help. We will have a URL showing all occurrences for a value - for example, all x mentions of the place y in our corpus. The occurrences are first shown as a number, let's say 7. The number is a link, and when we follow the link, we see the list of segments where the place is mentioned (a, b, c... all seven of them). The question is: what else to show, beside the CITE URN for places a, b, c... and the CTS URN for the segment? What would be useful? Once we have the CITE URN for the segment, we have access to everything, to all notes linked to the URN - what would you like, what would you need to see? The context, the periods, the word forms, the morphology, the lemmata, the standard place names...? Ideas are welcome!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nevenjovanovic/croala-pelagios/issues/49, or mute the thread https://github.com/notifications/unsubscribe-auth/AFTY4es6Vng02nq3OGMgFnDZrCSY3bhEks5rFtvMgaJpZM4LGyGg .

[nevenjovanovic]

A draft is here: croala.ffzg.unizg.hr/basex/cp-loci-cite/urn:cite:croala:loci.locid26446 (for the CITE URN urn:cite:croala:loci.locid26446), accessible (from one direction) through a list such as croala.ffzg.unizg.hr/basex/cp-loci-id/urn:cts:croala:bunic02.croala1761880.croala-lat2w.

I will add the lemmata and context now.

[NinaCengic]

In the light of the fact that we are doing this as a project under umbrella of linking places, I think that this time we could maybe choose to show the standard place names.

Otherwise, lemmata are a standard, of course.

2016-12-07 18:33 GMT+01:00 Neven Jovanović notifications@github.com:

A draft is here: croala.ffzg.unizg.hr/basex/cp-loci-cite/urn:cite:croala: loci.locid26446 (for the CITE URN rn:cite:croala:loci.locid26446), accessible (from one direction) through a list such as croala.ffzg.unizg.hr/basex/cp-loci-id/urn:cts:croala: bunic02.croala1761880.croala-lat2w.

I will add the lemmata and context now.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nevenjovanovic/croala-pelagios/issues/49#issuecomment-265514750, or mute the thread https://github.com/notifications/unsubscribe-auth/ALfJXmRkUI76v3jBRX07VvUeete2Rq5Rks5rFu3igaJpZM4LGyGg .

[nevenjovanovic]

@NinaCengic and @arsimr16 - I have followed your suggestions. I would like to somehow squeeze the periods in too, but the space is cramped already; check out now the URL listed above. I think I will use the CITE URN ana as the hyperlink behind the CTS URN (though this is a bit inconsistent).

[NinaCengic]

Now it looks rather crowded, but first, it's not bad per se.

If we look how to 'improve' it, or modify it, I would prefer to drop the context. It stands out a bit as a different kind of information here. I would try and see how it worked with just cite urn, cts urn, lemma, place name, time period and a link to the context, morphology, and the word forms (a sort of first-hand, basic information first, and then links to more detailed explanations).

2016-12-07 20:17 GMT+01:00 Neven Jovanović notifications@github.com:

@NinaCengic https://github.com/NinaCengic and @arsimr16 https://github.com/arsimr16 - I have followed your suggestions. I would like to somehow squeeze the periods in too, but the space is cramped already; check out now the URL listed above. I think I will use the CITE URN ana as the hyperlink behind the CTS URN (though this is a bit inconsistent).

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nevenjovanovic/croala-pelagios/issues/49#issuecomment-265544105, or mute the thread https://github.com/notifications/unsubscribe-auth/ALfJXsXvagfDvfG4v3vH3FdkMdLRrJC_ks5rFwZJgaJpZM4LGyGg .

[nevenjovanovic]

@NinaCengic - the period field is added. It is indeed a bit crowded now, but to me the context is quite useful, both for control and as an argument for our annotations.

[NinaCengic]

Great! If the context is useful as an argument for our comments, that we say, no, it's not crowded, we just go along the nije-beg-cicija road.

But, if we want to have it like that, is it possible to 'hide' cts and cite somewhere, behind a link of a sort, like CTS URN and CITE URN? As the same type of phenomena class.

I was now considering the column 'form', if we could do something about it. It seems a bit redundant if we present it together with the context...

2016-12-07 21:23 GMT+01:00 Neven Jovanović notifications@github.com:

@NinaCengic https://github.com/NinaCengic - the period field is added. It is indeed a bit crowded now, but to me the context is quite useful, both for control and as an argument for our comments.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nevenjovanovic/croala-pelagios/issues/49#issuecomment-265562683, or mute the thread https://github.com/notifications/unsubscribe-auth/ALfJXjQVeczKay42RaDJitUdB3BY0v5Gks5rFxW9gaJpZM4LGyGg .

[zeljkasalopek]

I wouldn't add any more fields. I would leave both "form" and "lemma" as they sometimes differ (one or more words). I think the "context" is useful, and "period" should definitely stay as it is one of the things we are trying to draw attention to. I agree with Nina, it would be great if the cts urn and/ or the annotation creator columns could be more narrow. I don't have much experience with this, but is it possible the cts urn to be for example in three rows instead of two? As for annotation creator, if we don't have to do it one by one, maybe we could put just "orcid" (or initials) - an expression that links to the specific orcid page...

The page to which the cts urn leads, with all the annotations, looks great!

Unfortunately, I think I will not be able to look at this more carefully again tomorrow before the meeting. See you then!

[NinaCengic]

Considering our Locus occurit in CroaLa page this morning, I think that we could remove period.

I am looking forward to seeing you in the afternoon!

2016-12-07 23:47 GMT+01:00 zeljkasalopek notifications@github.com:

I wouldn't add any more fields. I would leave both "form" and "lemma" as they sometimes differ (one or more words). I think the "context" is useful, and "period" should definitely stay as it is one of the things we are trying to draw attention to. I agree with Nina, it would be great if the cts urn and/ or the annotation creator columns could be more narrow. I don't have much experience with this, but is it possible the cts urn to be for example in three rows instead of two? As for annotation creator, if we don't have to do it one by one, maybe we could put just "orcid" (or initials) - an expression that links to the specific orcid page...

The page to which the cts urn leads, with all the annotations, looks great!

Unfortunately, I think I will not be able to look at this more carefully again tomorrow before the meeting. See you then!

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/nevenjovanovic/croala-pelagios/issues/49#issuecomment-265598393, or mute the thread https://github.com/notifications/unsubscribe-auth/ALfJXtP0Yj18LG9aB6otuGbEpeoytsu2ks5rFzeUgaJpZM4LGyGg .