Page MenuHomePhabricator

UW support for other templates than {{Information}} (eg {{Artwork}})
Open, LowPublic

Description

UploadWizard should support specialized description templates such as {{Artwork}}, in replacement of {{Information}}.

In order not to clutter the interface, this could be done using Upload Campaigns.

(P.S. I would have thought there was already a bug for that, but did not find any).


Version: unspecified
Severity: enhancement
See Also:
T49561: Book upload customization
T31955: Make UploadWizard compatible with local copyright tags (including fair use?)

Details

Reference
bz49443
Related Gerrit Patches:
mediawiki/extensions/UploadWizard : masterWill allow dynamic form generation in the details step

Event Timeline

bzimport raised the priority of this task from to Normal.Nov 22 2014, 2:09 AM
bzimport added a project: UploadWizard.
bzimport set Reference to bz49443.
bzimport added a subscriber: Unknown Object (MLST).
JeanFred created this task.Jun 11 2013, 4:38 PM

What is the current status of this? I see there is activity on the Gerrit patchset ; is there anything where we could help?

(In reply to Jean-Fred from comment #3)

What is the current status of this? I see there is activity on the Gerrit
patchset ; is there anything where we could help?

It's iffy.

Template support basically rests on the assumption that we'll be using templates long-term to do metadata storage - which is a bad assumption, though we don't yet know *how* bad.

I'll initiate a conversation on Multimedia-l about Wikidata on Commons once I see the appropriate signals go through where they need to; currently I don't think everyone's in the loop about this, and we definitely haven't made any decisions.

(In reply to Mark Holmquist from comment #4)

I'll initiate a conversation on Multimedia-l about Wikidata on Commons once
I see the appropriate signals go through where they need to; currently I
don't think everyone's in the loop about this, and we definitely haven't
made any decisions.

Has that happened? If so, archive link welcome.

TheDJ added a comment.Aug 25 2014, 9:48 PM

This project is picking up some speed and all information is being tracked from: https://www.mediawiki.org/wiki/Multimedia/Structured_Data

I think it is safe to assume that adding Artwork support is currently looking unlikely, favoring investing in structured data support for Commons.

Steinsplitter moved this task from Incoming to Uploading on the Commons board.Mar 11 2015, 12:54 PM
JeanFred raised the priority of this task from Normal to High.Apr 19 2015, 1:33 AM

The patch needs some cleanup, including migration to JSON l10n format. https://gerrit.wikimedia.org/r/66561

However, are we really going to hardcode even more Commons templates into the UploadWizard extension itself? Wouldn't it be vastly better to allow such data/mapping to be maintained on-wiki, perhaps in a MediaWiki page as the Campaigns extension does or in a special page or in collaboration with the TemplateData extension?

Change 66561 had a related patch set uploaded (by Nemo bis):
Will allow dynamic form generation in the details step

https://gerrit.wikimedia.org/r/66561

MarkTraceur lowered the priority of this task from High to Low.Jul 29 2015, 5:03 PM

I think this is going to be obviated soon, with the emergence of more specialized upload tools for specialized cases like artwork. We should be able to do it more easily outside of UploadWizard.

Restricted Application added subscribers: Steinsplitter, Matanya, Aklapper. · View Herald TranscriptJul 29 2015, 5:03 PM
Jdforrester-WMF moved this task from Untriaged to Backlog on the Multimedia board.Sep 4 2015, 6:12 PM

Change 66561 abandoned by Bartosz Dziewoński:
Will allow dynamic form generation in the details step

Reason:
I don't think this can be rescued, sorry :(

https://gerrit.wikimedia.org/r/66561

matmarex updated the task description. (Show Details)Sep 23 2015, 5:21 PM
matmarex removed a project: Patch-For-Review.
matmarex set Security to None.
matmarex removed a subscriber: wikibugs-l-list.

I think this is going to be obviated soon, with the emergence of more specialized upload tools for specialized cases like artwork. We should be able to do it more easily outside of UploadWizard.

Really not intending to be snarky, but: 2 years later, where are those "more specialized upload tools for specialized cases"? If they exist, none of them seems to be listed at Commons:Upload tools.

RP88 added a subscriber: RP88.Aug 19 2017, 8:19 PM
Jane023 added a subscriber: Jane023.EditedNov 15 2017, 9:13 AM

This issue will not go away with Structured Commons, just to be clear on that. To help understand this issue, here is a mapping from the artwork template to Wikidata using an example from a 17th-century painting: https://commons.wikimedia.org/wiki/File:Commons_vs_Wikidata_for_PD-Art-100-1923_images.png

added to https://meta.wikimedia.org/wiki/2017_Community_Wishlist_Survey/Wikidata#Integrate_Pattypan_and_Quick_Statements

TheDJ added a comment.Nov 15 2017, 9:35 AM

@Jane023 true, BUT it's easier to write tools that work and scale, when you are working with a predictable structure. If I can code: "Add widget that lists P186 to upload form", instead of having to deal with wiki text and arbitrarily configured json files, then short term, that's easier and long term, its more maintainable.

But in the end, if you make things complicated, then it's not easy to "uncomplicated" them with some UI sprinkles, that is true.

@Jane023 true, BUT it's easier to write tools that work and scale, when you are working with a predictable structure.

What is unpredictable about the image that I linked above? I noticed that the recent proposer in the 2017 wishlist also wants it for paintings. I like paintings and apparently so do a lot of other people, considering how many we have on Wikidata and how many we have yet to do that are currently locked in information templates on Commons.

@Jane023 the picture isn't unpredictable. The wiki text and the interpretation of that wiki text is (That's exactly what structured data is all about....).

So yes, if the argument is "I want this", then there are no blockers for making another few exceptions and flows in the UI. But if we want to design products with a purpose and want them to fit in with a strategic direction, then we are spending time where it won't have return of investment in the long term and we might need to reimplement later on. However, I see no evidence of anyone willing to invest in either, so i'd say there is little point in discussing potential implementation solutions.

Ah I believe you are confusing the two issues - future software implementations and current backlog cleanup drives paired with reducing future backlog. Implementation of this will at least allow people to correct the stuff they upload (or have already uploaded with the default uploader).

yeah i understand if you have never tried to clean the metadata mess at commons, you would not see the point to the task.
the workaround currently is to use pattypan and not use upload wizard.
it takes some expertise to know not to use the tool, that does not support linking to wikidata.

TheDJ added a comment.Nov 15 2017, 8:10 PM

@Slowking4 I was one of the three people who created all template logic for our metadata. It was my idea to do the whole metadata cleanup drive. I maintained UW for a few years. I was invited to the initial meetings where we discussed the ideas of structured commons and then decided that we shouldn't do it for a few more years... I think i know what i'm talking about.

i think it is great that you know enough to file a "will not fix"
i guess i will stop making what little metadata cleanup i was doing by hand,
steering newbies to a cul-de-sac that creates more backlog is not isolated to this process.
i'm sure you will have a solution for this metadata debt in you own time.

and i added this to the wishlist yet again this year, if you would care to respond. https://meta.wikimedia.org/wiki/2017_Community_Wishlist_Survey/Multimedia_and_Commons

TheDJ added a comment.EditedNov 15 2017, 9:41 PM

This is no about me. It's about keeping things separate.
1: fulfill short term goal
2: fulfill long term goals.

This ticket was originally picked up and discussed with a long term viewpoint in mind by the multimediateam. As such the Structured data ideas were related to this. After 2014 this ticket was derailed because due to multimediaviewer we suddenly didn't have a multimedia team any longer, causing any investment in Commons to die with it. If the community wishes to get this fixed through the wishlist, then that turns this ticket in the realization of a short term goal. But then you can dismiss anything that was written about this ticket between when it was opened and november of this year, because most of that had to do with realizing longterm goals.

As such I felt I had to explain to @Jane023 that bringing structure data into this discussion is irrelevant Long term goals and short term fixes rarely go hand in hand.

[edit] lemme rephrase that. @Jane023's original comment led me to believe she figured that structured data was not relevant to the solution strategy discussed in this ticket. I disagreed with that and tried to explain that the previous mentions of structured data had a logical origin and had fundamental technical benefits for the long run.

Then it turns out that people are bringing this up in the context of the survey; The survey is about short term investment, and that would certainly be possible here. it is my conviction however that a short term solution here is a waste of investment and only creates further burden,, as since we are now all in on Commons data again (long term), we would need to reimplement this later on.

Filed https://meta.wikimedia.org/wiki/2017_Community_Wishlist_Survey/Multimedia_and_Commons/Improve_UploadWizard_campaigns . Shouldn't be too hard to do and would add the flexibility to upload other templates without cluttering up the main work flow.

Ankry awarded a token.Dec 7 2017, 8:47 AM
Ankry added a subscriber: Ankry.