Community Wishlist Survey 2022/Wikidata/Entity Draft Namespace
The survey has concluded. Here are the results!
Entity Draft Namespace
- Problem: There is no way to create draft entities on Wikidata
- Proposed solution:
- Create dedicated entity draft namespaces for Wikibase for Items, Properties, and Lexemes appropriately named "Item draft", "Property draft", "Lexeme draft". These will contain entity pages identical in form to their normal types. You will be able to add statements, change labels, etc. and they will have a Discussion page. Draft entities can be used as values in statements on other draft entities but not normal entities. Draft entities' statements' property and item autocomplete search fields should show Draft entities in their results.
- Rename the new "Property draft" namespace on Wikidata to "Property proposal". "Property proposal" property pages will replace the current template-based property proposals. Users will create a proposal by creating a new page in the "Property proposal" namespace. They will add statements to the property just as they intend the property to look when copied to main "Property" namespace. Because draft entities can reference other draft entities, property proposals will be able to usefully use other property proposals and draft items in their statements. For example, if a property and subproperty is being proposed at the same time, the subproperty's proposal can add the subproperty of (P1647) statement and link to its parent property's proposal. Additionally, if a new data structure is going to be created from a property, the property's usage examples can use draft items that may not be appropriate to put into the database yet. The user will explain their motivation and discussion about the proposal on the proposal's Discussion page. Proposals will be categorized by subject and status from a template added to the Discussion page that adds the appropriate categories. When a property is ready to be created, a property creator will use a tool to copy the "Property proposal" entity page to a new property in the "Property" namespace. The proposal page will remain for historical preservation.
- Who would benefit:
- Property creators
- All editors
- Data importers
- More comments:
- Having dedicated entities will also allow the querying for proposals and their data - something we can't easily do at the moment due to data being managed by templates and categories.
- Other organizations that use Wikibase also may find use of this. They may not want all data published to the main entity namespaces and may want to experiment or verify new parts of their ontologies or data about to be added. These namespaces allow them to do this without requiring them to setup a separate instance of Wikibase.
- Phabricator tickets: phab:T298405
- Proposer: Lectrician1 (talk) 21:07, 10 January 2022 (UTC)
I have hesitated to start writing property proposals because I neither wanted to setup up a document to store my draft, nor finish it all in one session. Of course having a draft space would fix that. Blue Rasberry (talk) 21:19, 11 January 2022 (UTC)
The <translate></translate> tags are currently not rendered correctly here. I have created Community Wishlist Survey 2022/Translation/Make "translate" tags always render correctly for addressing this issue. GeoffreyT2000 (talk) 15:14, 22 January 2022 (UTC)
- Support —The Editor's Apprentice (talk) 18:53, 28 January 2022 (UTC)
- Support Bluerasberry (talk) 19:49, 28 January 2022 (UTC)
- Support I like the idea of having a sandbox equivalent that's not a Wikidata Sandbox item. Drafting property proposals can be collaborative and sorting that out *before* community input would be nice (and probably help address issues before the community even needs to weigh in). Wskent (talk) 19:57, 28 January 2022 (UTC)
- Support Aca (talk) 15:50, 29 January 2022 (UTC)
- Support Nw520 (talk) 23:31, 29 January 2022 (UTC)
- Support Joshbaumgartner (talk) 00:09, 30 January 2022 (UTC)
- Support Dhx1 (talk) 00:17, 30 January 2022 (UTC)
- Support This would allow me to demo alternate ways of modelling a subject area, mixing in real properties and values from non-draft space. Pelagic (talk) 09:02, 30 January 2022 (UTC)
- Support This could also help model changes to existing entities, i.e. the draft could use a current property for a template and allow trying out alternative constraints which could be worked into the original property after community approval of the draft. SM5POR (talk) 09:44, 30 January 2022 (UTC)
- Support I think this would be a better alternative than the "Property proposal helper script" idea also suggested this year. Property creators would need to have the ability to move properties from draft to non-draft namespace. ArthurPSmith (talk) 15:53, 31 January 2022 (UTC)
- Support Silver hr (talk) 20:55, 2 February 2022 (UTC)
- Support Drafts would ease workflow. Rotavdrag (talk) 11:06, 3 February 2022 (UTC)
- Support Drafts to approve items and properties Thingofme (talk) 14:31, 4 February 2022 (UTC)
- Support - Darwin Ahoy! 19:37, 4 February 2022 (UTC)
- Support Drafts are good everywhere. Daniel Case (talk) 23:09, 5 February 2022 (UTC)
- Support Redalert2fan (talk) 14:51, 6 February 2022 (UTC)
- Support Ayumu Ozaki (talk) 04:02, 7 February 2022 (UTC)
- Support Marcok (talk) 07:25, 10 February 2022 (UTC)