User talk:Charles Faulhaber: Difference between revisions

From FactGrid
Jump to navigation Jump to search
 
No edit summary
Line 5: Line 5:
here the exemplary items you might try to refine:
here the exemplary items you might try to refine:


[[Item:Q164502]]
* [[Item:Q164502]]
[[Item:Q164746]]
* [[Item:Q164746]]
[[Item:Q164748]]
* [[Item:Q164748]]


there are probably some statements I would try to use if it was my project especially the [[Property:P233]]/+[[Property:P234]]  option to create a stemma. This is something I am not quite sure how it will work out.
there are probably some statements I would try to use if it was my project especially the [[Property:P233]]/+[[Property:P234]]  option to create a stemma. This is something I am not quite sure how it will work out. If you talk to computer people they might find that easy. [[Property:P233]] states the previous position(s) in a genetic relationship and [[Property:P234]] is a property to qualify the respective genealogical link like: translation, abbreviation and so on. We manages to get network graphs with these two properties but I'd love to ave a visualisation that exploits the P106 date marker to create the tree...
 
If you talk to computer people they might find that easy. [[Property:P233]] states the previous position(s) in a genetic relationship and [[Property:P234]] is a property to qualify the respective genealogical link like: translation, abbreviation and so on.
 
We manages to get network graphs with these two properties but I'd love to ave a visualisation that exploits the P106 date marker to create the tree...


There are other issues I did not try to solve. The [[Property:P476]] identifier should be able to link straight through into the dataset. You can configure it  if you  know more about how your software is creating these dynamic links. (That is also the reason why I did not create the "Uniform Title IDno" - you people will know better how to create links into your database.
There are other issues I did not try to solve. The [[Property:P476]] identifier should be able to link straight through into the dataset. You can configure it  if you  know more about how your software is creating these dynamic links. (That is also the reason why I did not create the "Uniform Title IDno" - you people will know better how to create links into your database.

Revision as of 13:44, 27 May 2020

Data model

Dear Charles,

here the exemplary items you might try to refine:

there are probably some statements I would try to use if it was my project especially the Property:P233/+Property:P234 option to create a stemma. This is something I am not quite sure how it will work out. If you talk to computer people they might find that easy. Property:P233 states the previous position(s) in a genetic relationship and Property:P234 is a property to qualify the respective genealogical link like: translation, abbreviation and so on. We manages to get network graphs with these two properties but I'd love to ave a visualisation that exploits the P106 date marker to create the tree...

There are other issues I did not try to solve. The Property:P476 identifier should be able to link straight through into the dataset. You can configure it if you know more about how your software is creating these dynamic links. (That is also the reason why I did not create the "Uniform Title IDno" - you people will know better how to create links into your database.

I also did not go into details with the two texts of the manuscript. Item:Q164746 has some blanks "Input here" that just indicate we could do it, but I did not create the respective items because that would open ever new boxes. The language item "Castellano" might need specification (Spanish would also have been available, but I guess you have more specific terms for different historical periods like we have in German with Middle High German, or Middle Low German).

Best Wishes --Olaf Simons (talk) 13:42, 27 May 2020 (CEST)