Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What data to include in Life Version? #3

Closed
mfranke93 opened this issue Dec 22, 2021 · 40 comments
Closed

What data to include in Life Version? #3

mfranke93 opened this issue Dec 22, 2021 · 40 comments
Assignees
Labels
help wanted Extra attention is needed question Further information is requested

Comments

@mfranke93
Copy link
Collaborator

Initially opened by gs108488 in 211@TIK. History:

gs108488 Dec 15, 2021:

Similar to issue #172, we need to define which data is included in the Life Version?

@mfranke93 mfranke93 added help wanted Extra attention is needed question Further information is requested paused This issue is paused, waiting for external input or events. labels Dec 22, 2021
@tutebatti
Copy link
Collaborator

"Persons" should not appear in the Public Version. Right, @rpbarczok?

@tutebatti tutebatti assigned tutebatti and mfranke93 and unassigned tutebatti Jan 10, 2022
@mfranke93 mfranke93 removed their assignment Jan 10, 2022
@rpbarczok
Copy link

Yes, they should not.

@tutebatti
Copy link
Collaborator

Thank you. @rpbarczok , please also see the original question referred to in the first post here, with linking to #172 in the old repository of the github instance hosted by Uni Stuttgart.

@rpbarczok
Copy link

@mfranke93: Would it be a problem if I changed the short titles of the sources. At the moment they are not very self explanatory or in German.

@mfranke93
Copy link
Collaborator Author

Not at all.

@mfranke93
Copy link
Collaborator Author

mfranke93 commented Jan 19, 2022

  1. Only the following tags should be visible:

@rpbarczok What about the tag Metropolitan Residence?

Also, since you mentioned something about renaming the source short names yesterday, please make sure the source list is spelled correctly here. Right now, there are 31 sources in your list, but only 28 in the database that exactly match those short names.

@mfranke93
Copy link
Collaborator Author

mfranke93 commented Jan 19, 2022

These four tags from your list do not exist:

First degree capital
Metropoliten residence
Second degree capital
Third degree capital

I assume the capitals miss the hyphen (first-degree...) and the other should be "metropolitan",

The sources are fine now.

@rpbarczok
Copy link

And again:
Evidences:

All evidences that are visible and marked by the tag "DhiMu"

Only the following tags should be visible:

Bishopric
Metropolitan see
Patriarchate
Diocese without specified ranking
Part of an episcopal see
Episcopal residence
Metropolitan residence
Patriarchal residence
First-degree capital
Second-degree capital
Third-degree capital
Mosque or Madrasa
Synagogue or Yeshiva or Beth Midrash or Beth Din
Church or Monastery
Reviewed

Following sources:

Fiey, OCN
DHGE
EI 2
EIran
EJ
AKg
TIB 5
CE
EI 1
EI 3
TIB 15
Vest, Melitene
TIB 2
Munier, Eglise copte
EJIW
Hamilton, Latin Church
Timm, Christlich-koptische Ägypten
Muqaddasi (arab.)
Muqaddasi (engl.)
Synode of Sis 1307 (lat.)
Synode of Sis 1307 (arm.)
Synode of Adana 1316 (lat.)
Synode of Adana 1316 (arm.)
Synode of Sis 1342 (lat.)
Benjamin of Tudela (engl.)
Benjamin of Tudela (hebr.)
PmbZ
Letter by Benedictus XII 1341 (lat.)
Coronation of Levon I (fr.)
Council of Hromklay 1179
Schick, Christian Communities of Palestine

@UniStuttgart-VISUS UniStuttgart-VISUS deleted a comment from rpbarczok Jan 19, 2022
@UniStuttgart-VISUS UniStuttgart-VISUS deleted a comment from rpbarczok Jan 19, 2022
@mfranke93
Copy link
Collaborator Author

I'm not sure where you keep copying this from, but please stop, because I have to copy it out of here again, and there are still typos in there. I started keeping my own list based on the database even with the old issue at TIK.

To summarize:

  • Regarding tags, nothing changes as opposed to the old status: Remove the tags DhiMu, Annotator beta test, eOC, Non-residential, Community.
  • Keep evidence from the sources in the list above, and the sources themselves.

@rpbarczok
Copy link

I copied it from the visualisation.

To your summary: Yes

@mfranke93
Copy link
Collaborator Author

mfranke93 commented Jan 19, 2022 via email

@rpbarczok
Copy link

OK. Understood. Sorry for the mess. I am in some stress at the moment, since I have to organize my departure from the project.

It does only affect the sources and the tags, though?

@mfranke93
Copy link
Collaborator Author

OK. Understood. Sorry for the mess. I am in some stress at the moment, since I have to organize my departure from the project.

Understandable, and no problem. I just want to make sure we don't accidentally include too little data in the public version (by excluding a source or the like).

It does only affect the sources and the tags, though?

Yes. There is other stuff going on when doing the data cleanup, but it all bases on the set of tags and sources to include. For reference, here is the current SQL script for doing that. However, I need to add the person stuff, because for the reviewer version, there were still persons involved.

@tutebatti @rpbarczok This comment regarding persons not being included: Does that affect the DaRUS export as well, or do we include the persons there?

@tutebatti
Copy link
Collaborator

Since the DaRUS export is what we will be cited with and the data other people will (re)use - as far as I understand at least -, I would not include persons nor anything which is still somehow "work in progress" or does not figure under the label DhiMu, e.g. is in the scope of eOC.

@rpbarczok
Copy link

I believe that we have added people only for Bar Hebraeus and Michael the Great so far, and these sources are not part of the DhiMu. So, the people in the repository would be without any connection to any evidence.

@rpbarczok
Copy link

Ok, I just looked it up, there is at least one bishop connected to some evidences, but I would agree with Florian. We only added a few people for testing the process, so there is no gain in adding them

@mfranke93
Copy link
Collaborator Author

Since the process for exporting the data is removing unneeded stuff rather than just adding what is needed: Am I correct to say: for the public version and the DaRUS dump, all person data should be removed?

@rpbarczok
Copy link

yes

@mfranke93
Copy link
Collaborator Author

Okay. I have modified and tested the export script, and everything looks good. Just let me know when you are done checking the names.

@mfranke93 mfranke93 added this to To do in Public Instance at HU via automation Jan 20, 2022
@rpbarczok
Copy link

As you have mentioned it in issue #92: I haven't thought about the fact that all the places are in the Darus dump. I thought since places without evidence are not visible on the map, they just something I do not have to concern with. Sorry for the premature assumption.
So: Please remove all places from the live version und the Darus dump that have no evidence with an DhiMu tag!

@rpbarczok
Copy link

I want to summarize the above discussion: Basically all information are already mentioned above, with one exception: We changed the short title of the sources and added two additional sources. To minimize misunderstandings, I added the primary key to the tags and the sources.
Concerning the data dump for Darus and consequently in the DB of our live web application will contain:
1.) all pieces of evidence that a) have the tag DhiMu (16) and b) are connected to a specified set of sources.
2.) The specific set of sources contains following sources: OrChrN (1), DHGE (2), EI² (3), TIB15 (15), EI (13), Timm (26), EJ (5), Vest (16), PMBZ (42), Hamilton (25), Munier (19), Muqaddasi ara (29), Muqaddasi eng (30), EJIW (20), EIr (4), CoptEnc (11), TIB5 (10), EI³ (14), Schick (63), TIB2 (17), Benjamin eng (40), Benjamin heb (41), Sis 1307 lat (34), Sis 1307 arm (35), AtKG (8), Hromklay 1179 (58), Smbat 1199 fra (57), Sis 1342 lat (39), Adana 1316 arm (37), Adana 1316 lat (38), Benedictus PP. XII (43), Crown (68), Richter-Bernburg (69).
3.) Data that are not connected to these evidences should not be part of the data dump. That means that all places that do not have a piece of evidence that is described by 1.) are to be removed from the dump.
4.) All person data should be removed.
5.) The following tags have to be removed: Community (11), DhiMu (16), eOC (17), Non-residential (19), Annotator beta test (100)
6.) Concerning the religious group of 12S, 7S, 5S.
a. If possible: In the Visualisation they should be treated as Shia (also in respect to the filter function), in the dump the data should be stay as they are.
b. If a. is not possible (or if only possible with considerable amount of work) we have to remove the mentioned group and add the specifics in the religion instance comment.

We are still not finished with the revision of the data, so I have to ask for your patience concerning the final data dump

@mfranke93
Copy link
Collaborator Author

Looks good to me.
Regarding 6:

a. If possible: In the Visualisation they should be treated as Shia (also in respect to the filter function), in the dump the data should be stay as they are.

Possible in theory, but I really do not want to do that. The software should stay data-agnostic.

b. If a. is not possible (or if only possible with considerable amount of work) we have to remove the mentioned group and add the specifics in the religion instance comment.

Would that only happen for the exported data, or for the production database as well? We can automate this as well, one question though: what would happen if there is already a religion instance comment?

@tutebatti
Copy link
Collaborator

We can automate this as well, one question though: what would happen if there is already a religion instance comment?

If that is possible, this would be preferable, I'd say. Since the information in the column religion instance comment is not structured in any machine-readable way, I would suggest to add the strings 12S, 7S, and 5S, respectively, at the beginning of the comment column followed by a semicolon and space (; ) and move the rest of the content of that column behind it.

@rpbarczok
Copy link

I agree.

@mfranke93
Copy link
Collaborator Author

mfranke93 commented Mar 10, 2022

Okay. What about if there is no place religion instance comment? Would you then rather have the comment be 7S, or 7S; ? Slight bikeshedding here, but I'd rather ask ;D

@tutebatti
Copy link
Collaborator

tutebatti commented Mar 10, 2022

Got us there! I would then omit the ; . However, you mean religion instance comment, right? (Got you back? ;) )

@rpbarczok
Copy link

One question: Would it be possible to transform 5S to Zayidiya, 7s to Isma'iliya and 12S to Imamiya. That would be more conform to the names we use in the comments.

@mfranke93
Copy link
Collaborator Author

You mean specifically for the comments, right? Like: Imamiya; this is the rest of the religion instance comment

@rpbarczok
Copy link

Exactly

@tutebatti tutebatti removed the paused This issue is paused, waiting for external input or events. label Mar 10, 2022
@mfranke93
Copy link
Collaborator Author

No problem at all. To summarize:

  1. Religion instances of 5S, 7S and 12S change to being instances of SHIA. Their comments get prepended with "Zayidiya; ", "Isma'iliya; ", and "Imamiya; ", respectively. If the religion instance comment is empty to start with, the semicolon and space at the end are omitted.
  2. The religions 5S, 7S, and 12S are dropped.

@rpbarczok
Copy link

Yes, perfect.

@tutebatti
Copy link
Collaborator

Just to be sure: This only happens via the export. The data in the production database stays as is, right?

@mfranke93
Copy link
Collaborator Author

Just to be sure: This only happens via the export. The data in the production database stays as is, right?

That is what wanted to know here, but for the ensuing discussion, I assumed that this only applies to the data export. To be sure, please confirm that is what you meant as well, @rpbarczok .

I wouldn't do such an invasive edit to the production database without making sure that is actually what you wanted, do not worry 😄

@tutebatti
Copy link
Collaborator

I wouldn't do such an invasive edit to the production database without making sure that is actually what you wanted, do not worry

Would have never thought that, but to do bikeshedding as well I wanted to add that to the summary. ;)

@rpbarczok
Copy link

I confirm.

@mfranke93
Copy link
Collaborator Author

mfranke93 commented Mar 10, 2022

Update: For the current database state, the Shia changes affect 28 36 entries. I have listed them below, how they would look after the proposed change. If you see any issues with the data (like the comments of 4433 or 1431), you can fix them via GeoDB-Editor quite easily now.

evidence_id place_name religion time_spans religion_instance_comment
4359 Multan Shia {"[900,1176)"} Isma'iliya
4291 Makka Shia {"[951,1347)"} Zayidiya
4433 Samarra Shia {"[848,1401)"} Imamiya; Imamiyya, since 941 Twelver Schia
1616 al-Ahsa Shia {"[926,1077)"} Isma'iliya
4616 al-Ahsa Shia {"[900,1075)"} Isma'iliya
9579 Afamiya Shia {"[1095,1096)"} Isma'iliya
9813 al-Rayy Shia {"[865,886)"} Zayidiya
9818 al-Rayy Shia {"[865,886)"} Zayidiya
1189 al-Ahwaz Shia {"[899,1001)"} Isma'iliya
1303 Isfahan Shia {"[1100,1126)"} Isma'iliya
1304 Isfahan Shia {"[1098,1104)"} Isma'iliya; Batiniyya
1317 Isfahan Shia {"[1072,1195)"} Isma'iliya
1261 Bukhara Shia {"[1044,1046)"} Isma'iliya
1446 Kashan Shia {"[1198,1199)"} Imamiya
1431 Samarra Shia {"[848,1401)"} Imamiya; Imamiyya since 941 Twelver Shia
1441 Nahawand Shia {"[1300,1401)"} Imamiya
1470 Qayin Shia {"[1040,1401)"} Isma'iliya
1617 al-Ahsa Shia {"[913,914)"} Isma'iliya
1522 Halab Shia {"[1120,1121)"} Isma'iliya
1521 Halab Shia {"[944,1071)"} Imamiya
1525 Halab Shia {"[900,1151)"} Imamiya
1543 San'a' Shia {"[1047,1174)"} Isma'iliya
1544 San'a' Shia {"[1381,1401)"} Zayidiya
1546 San'a' Shia {"[1061,1177)"} Isma'iliya
1547 San'a' Shia {"[1375,1401)"} Zayidiya
1614 al-Ahsa Shia {"[926,1052)"} Isma'iliya
1552 Makka Shia {"[951,1347)"} Zayidiya
1538 Multan Shia {"[900,1176)"} Isma'iliya
1623 Suhar Shia {"[943,954)"} Isma'iliya
2617 Banyas Shia {"[1126,1131)"} Isma'iliya
2889 al-Hilla Shia {"[1262,1277)"} Imamiya
3271 al-Dinawar Shia {"[985,989)"} Zayidiya; 5er Shia (Zayidiyya) "[T]hey belong to the school of Sufyan al-Thawri."
3312 Jabala Shia {"[1165,1174)"} Isma'iliya
3289 Sa'da Shia {"[897,1401)"} Zayidiya
3550 al-Ahsa Shia {"[985,989)"} Isma'iliya
3834 Sa'da Shia {"[1200,1201)"} Zayidiya

@rpbarczok
Copy link

We changed the religion_instance_comment anyway, as Florian mentioned here. I am only confused that the German form "Apamea am Orontes" is displayed, I changed that to "Afamiya" some time ago.

@mfranke93
Copy link
Collaborator Author

mfranke93 commented Mar 10, 2022

We changed the religion_instance_comment anyway, as Florian mentioned #92 (comment). I am only confused that the German form "Apamea am Orontes" is displayed, I changed that to "Afamiya" some time ago.

Yes, my bad. I tested it on the testing database first, and that is where I got that output. I updated it for the production database, where it is 36 entries.

@rpbarczok
Copy link

OK, I changed the comments of the 4433, 1431 and 3271 in our religion_comment.csv accordingly.

@tutebatti
Copy link
Collaborator

I think we can close this, right? @mfranke93 @rpbarczok

Public Instance at HU automation moved this from In progress to Done Mar 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed question Further information is requested
Projects
No open projects
Development

No branches or pull requests

3 participants