Help: Dataset
Forms and Templates[ ]
Category[ ]
Test Page[ ]
New Schema[ ]
category | order | property | label | var | Datatype | range | input type | is multi val | is uncertain | needs change | replaces prop | replaces var | Notes | Francesco approval |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Dataset | Property:Developed by | Developed by | Developed by | Page | Category:Person, Category:Institution | yes | yes | yes | Property:Developed by (people), Property:Developed by Institution | Developed by (people), Developed by, Developed by Institution | ok | |||
Dataset | Property:Has event | Has event | Has event | Page | Category:Event | tokens, with linkform to Category:Event | no | no | no | Property:Creation Date | Creation Date | In my opinion should be replaced by an event sub form, in which "creation date" is the descriptor of the event. Same with end date. It allows for the introduction of many other unpredictable events (suspended, interrupted, blocked by court, started again, etc.) | ||
Dataset | Property:Dataset Category | Dataset Category | is dataset category | Text | Property:Dataset Category | tokens | yes | yes | Property:is dataset category | is dataset category | Not sure what is happening with this one... | |||
Dataset | Property:URL | URL | URL | URL | text | no | no | no | ok | |||||
Dataset | Property:has full name | Dataset full name | has full name | Text | text | no | no | no | ||||||
Dataset | Property:Related | Related Products | Related Products | Page | Category:Products | tokens | yes | no | no | Property:Related_Technology | Shall the name “Technologies” be kept,since we renamed that category to “Products” ? | No we should rename everything to products. | ||
Dataset | Property:Owner | Owning institution | Owning institution | Page | Category:Institution | tokens | yes | yes | Yes, property | Property:Owning institution | ok | |||
Dataset | Property:Custodian | Custodian institution | Custodian institution | Page | Category:Institution | tokens | yes | yes | Yes, property | Property:Custodian institution | remove repetition in interface | ok | ||
Dataset | Property:Funding amount | Funding amount | has funding | Quantity | text | no | yes | yes | Property:has funding | Unit: € default, conversion to $ possible | ok For the unit: I think the best would be to be able to specify it. Maybe a point for discussion. | |||
Dataset | Property:Images amount | Images amount | has images | Number | text | no | yes | yes | Property:has images | ok | ||||
Dataset | Property:Employees amount | Employees amount | Employees amount | Number | text | no | yes | yes | Property:Has individuals | Datatype Number will not allow expressing ranges | Ok | |||
Dataset | Property:Runs product | Runs software | Runs software | Page | Category:Products | tokens | yes | yes | Yes, both | Property:Runs database software, Property:Runs search software | runs database software, runs search software | The software type can be discovered by querying the Property:Technology Type from Category:Products instances. Shall it be called “Runs software” or “Runs product”? | Ok. I would say "Runs software" is more intuitive maybe? Alternatively, call the variable Runs product and label it for the users "Runs software (product)"? Whichever will be less confusing I would say. | |
Dataset | Property:Country | Country | combobox | no | ok |
New schema discussion[ ]
Property:Creation Date[ ]
User:Francesco: Should be replaced by an event sub form, in which "creation date" is the descriptor of the event. Same with end date. It allows for the introduction of many other unpredictable events (suspended, interrupted, blocked by court, started again, etc.)
15:37, 22 April 2022 (CEST) : Since there is already an Category:Events with Form and template, would it make sense to use the values from that category, and have a formlink to that form if a new event needs to be created?
Now the question is what property shall be used to relate a Category:Dataset instance to an Category:Event instance?
- existing Property:Has event?
25.04.2022 User:Francesco: I would say existing Property:Has event if it can work.
- used (once) but undefined Property:Is related ?
Andre (talk) 16:50, 25 April 2022 (CEST) in discussion with User:Francesco it was decide to make
- Dataset related Events with subtemplate HasEvent like in Form:Deployment
Property:Related_Technology[ ]
Andre (talk) 15:56, 22 April 2022 (CEST) suggest using only Property:Related and restricting range of values to Category:Products instances
25.04.2022 User:Francesco: Sounds good!
Property:Dataset Category[ ]
User:Francesco: Not sure what is happening with this one.
Andre (talk) 15:37, 22 April 2022 (CEST) property seems used consistently (check its page) but it should be redefined as datatype Text and perhaps have a controlled list of values
25.04.2022 User:Francesco: Sounds good
Property:Keywords[ ]
User:Francesco: Are keyword needed? No. It was an experiment, but I don't think they are useful. They just proliferate without any logic, and are left empty most of the time.
Andre (talk) 15:37, 22 April 2022 (CEST) then lets not use it.
25.04.2022 User:Francesco: Agreed
Property:Funding amount [ ]
User:Francesco ok For the unit: I think the best would be to be able to specify it. Maybe a point for discussion.
15:37, 22 April 2022 (CEST) https://www.semantic-mediawiki.org/wiki/Help:Special_property_Corresponds_to#Positional_references has an example for converting $ and euros. We can do that. We can also add more currencies and their conversion rate as needed
25.04.2022 User:Francesco: That would be great. I don't want to make things too complicated, but there are two key pieces of information with this funding amount property: 1) how much (and in which currency) and 2) when. Turkish liras for exemple loose 20% of their value every year, so it really matters if we are speaking of a TL amount from 1992 or from 2020. I would also say that having both pieces of information could be very useful (ie. the original amount and the automatically converted amount). If it's too hard of course, just the original amount in original currency and date is enough.
Andre (talk) 11:56, 25 April 2022 (CEST): Adding this qualifier is tricky. Although it might need to reproduce the reality of currency value changes over time, but we cannot express that with a single property, we'd have to have an extra structure: subpobject or record property: where the currency, date and value and exchange rate to dollar or euro at that point is are present. In short is too complex. But we can talk about it, because we need to make some decisions about it.
Andre (talk) 16:50, 25 April 2022 (CEST) in discussion with User:Francesco it was decide to make
- Property:Funding of type Record:
- Property:Amount of money: of type Number
- Property:Currency: Text with controlled values (dollars,euro)
Property:Runs software[ ]
User:Francesco Ok. I would say "Runs software" is more intuitive maybe? Alternatively, call the variable Runs product and label it for the users "Runs software (product)"? Whichever will be less confusing I would say.
Andre (talk) 15:37, 22 April 2022 (CEST) let do Property:Runs product and label it Runs Software. I think is the simplest and most intuitive.
25.04.2022 User:Francesco: Perfect
issues with Deployment[ ]
Template, Form and Property name[ ]
User:Andre has to discuss these issues with User:Francesco
Andre (talk) 11:19, 18 April 2022 (CEST) comments
in deployments there is "if" function in plain-text which comes from the miss-formatted template Template:Dataset
See an example of the error in ABIS_(Croatia)
=> FR: Feel free to remove
In Template:Dataset if I look at the diffs 20Jan and 6April I see a few changes, that seem not very clear https://www.securityvision.io/wiki/index.php?title=Template%3ADataset&type=revision&diff=5619&oldid=5177
- I dont know what the {{!}} means (FR: me neither)
- variable names (between template could be simpler) for instance {{{Developed by (people)|}}} could be simplified to {{{devByPpl}}} (FR: ok)
- property names are messy:
- [[Developed by Institution::x]] - is good property name, but Property:Developed_by_Institution has been deleted and replaced by Property:Developed by
- [[Developed by::x]] - is not a good property name Property:Developed by
- typo
- use of parenthesis (should be avoided)
- use of plural "institutuions"
- Property:Developped_by_(people) comments above apply to the this property
=> FR: Feel free to modify as suggested in the table above