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
Comments
"Persons" should not appear in the Public Version. Right, @rpbarczok? |
Yes, they should not. |
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. |
@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. |
Not at all. |
@rpbarczok What about the tag 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. |
These four tags from your list do not exist:
I assume the capitals miss the hyphen (first-degree...) and the other should be "metropolitan", The sources are fine now. |
And again: All evidences that are visible and marked by the tag "DhiMu" Only the following tags should be visible: Bishopric Following sources: Fiey, OCN |
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:
|
I copied it from the visualisation. To your summary: Yes |
The problem is that for the data export, the comparison of texts is done exactly, so if the tag names or source short names do not match *exactly,* the data in question will just not be ignored. So I would suggest copy-pasting directly from pgAdmin or the visualization and not typing it. There is already a difference between “First degree capital” and “First-degree capital”, and also between “Metropolitan residence” (your capitalization) and “Metropolitan Residence” (DB and visualization capitalization). But I think we are in agreement now.
Keep in mind that, if you plan to rename some tags or continue editing the source short names, we will need to update this list again.
Von: rpbarczok ***@***.***>
Gesendet: Mittwoch, 19. Januar 2022 10:57
An: UniStuttgart-VISUS/damast ***@***.***>
Cc: Max Franke ***@***.***>; Mention ***@***.***>
Betreff: Re: [UniStuttgart-VISUS/damast] What data to include in Life Version? (Issue #3)
I copied it from the visualisation.
To your summary: Yes
—
Reply to this email directly, view it on GitHub<#3 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACHQP3XMY4FJHUBKESTTGZDUW2DHDANCNFSM5KSIHSHQ>.
Triage notifications on the go with GitHub Mobile for iOS<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
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? |
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).
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? |
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. |
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. |
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 |
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? |
yes |
Okay. I have modified and tested the export script, and everything looks good. Just let me know when you are done checking the names. |
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. |
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. We are still not finished with the revision of the data, so I have to ask for your patience concerning the final data dump |
Looks good to me.
Possible in theory, but I really do not want to do that. The software should stay data-agnostic.
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? |
If that is possible, this would be preferable, I'd say. Since the information in the column |
I agree. |
Okay. What about if there is no |
Got us there! I would then omit the |
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. |
You mean specifically for the comments, right? Like: |
Exactly |
No problem at all. To summarize:
|
Yes, perfect. |
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 😄 |
Would have never thought that, but to do bikeshedding as well I wanted to add that to the summary. ;) |
I confirm. |
Update: For the current database state, the Shia changes affect
|
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. |
Yes, my bad. I tested it on the |
OK, I changed the comments of the 4433, 1431 and 3271 in our religion_comment.csv accordingly. |
I think we can close this, right? @mfranke93 @rpbarczok |
Initially opened by gs108488 in 211@TIK. History:
gs108488 Dec 15, 2021:
The text was updated successfully, but these errors were encountered: