Modify

Opened 13 years ago

Closed 12 years ago

#1447 closed enhancement (fixed)

more support for source tag

Reported by: Schusch Owned by: framm
Priority: major Milestone:
Component: Core Version: latest
Keywords: Cc:

Description

in all dialogs when tags are created, a field for the source-tag should be offered. Giving a source for the data one adds to the database should be self-evident, and the usage will be brought forward by offering this tag;

(perhaps the source-tag should have a sort of history, but that theme is database related)

Greetings, Schusch

Attachments (0)

Change History (12)

comment:1 Changed 13 years ago by stoecker

Resolution: wontfix
Status: newclosed

I don't like that idea. It would make all dialogs more complicated.

comment:2 Changed 13 years ago by Schusch

Resolution: wontfix
Status: closedreopened

Well, maybe one person doesn't like it -

but it is very important to know, what the source of an information is - especially for the reliability of the information; it should be self-evident that everybody gives a hint to the source - so at least there should be a sort of reminder for the most important elements - these are roads, ways, waypoints, rail-tracks and waterways - as a start at least for the roads ... it is a reminder for everybody to tell us about the source - I think this concept works fairly gut in the de-wikipedia (reminder to add a coment to the edit) and it helps for better quality standards

comment:3 Changed 13 years ago by anonymous

gut in the de-wikipedia ;-) sorry for thisone ...

comment:4 Changed 13 years ago by framm

I am also against adding a source tag to everything but since most editing activity will use the same source within one editing session, we should perhaps investigate adding a "source" tag to changesets we create, i.e. you would be asked to provide a commit comment and an optional "source" specification when you hit upload.

comment:5 in reply to:  4 Changed 13 years ago by schusch

good idea - not perfect, but easier and faster - support from me :-)

(one hint: source-tags changed or set new in the actual session should not be overwritten by this general tag)

comment:6 Changed 13 years ago by Hasienda

more hints following the idea of adding/setting source values per session:

  • never mass-write source values to nodes
  • never change source value already changed by current command stack
  • user input/confirmation of common source value for elements of a requested upload as dialog, design as following:
Would you like to add general source information to this upload?

new common source value: [_combobox_]
   [ ]1 overwrite older source information too
 
[ ]2 don't remind me again
          [Yes] [No]

Comments

  • command button "No" selected by default, to skip whole dialog with <Enter>
  • combo(text input + list)box filled with all source values currently known by JOSM (downloaded as well as changed/creaded source information), 1st and always empty item selected by default
  • checkbox 1 inactiv by default, activated only, if and as long as combobox has value <> ""
  • checkbox 1 gives choice to write content of selected combobox item at
    • ways that have no source key yet, if deselected (by default)
    • all ways but those in the current command stack
  • checkbox 2 is
    • deselected by default
    • persistent, if selected and comitted once with Yes-buton
    • suppressing dialog all times, while selected, until reset somewhere in JOSM preferences by checking option "ask for common source value per upload"

comment:7 Changed 13 years ago by framm

There seems to be a misunderstanding here. We do not want to change the source tags of individual elements. We want to add a source tag to the changeset, which is a new feature that groups a number of changes with API 0.6. The "source" tags on individual elements will not be changed.

comment:8 in reply to:  7 Changed 13 years ago by anonymous

Replying to framm:

well - i still think an easy possibility (filling in not mandatory) for adding a source in the most used definitions should be given - a source is very important for a first impression on what that data is based and should therefore be strongly supported ...

(as i understand the last comment , there will come a possibility for commenting an upload - great)

comment:10 Changed 13 years ago by anonymous

I have a suggestion, just add a tick-box for source on all items, that remembers your last status (i.e if you usually put in source when editing rivers, this one is ticked, but when you edit lakes you don't) and have a different panel with a dropdown that remembers the sources you have used in the past. By default no sources and no values in the dropdown.

comment:11 in reply to:  10 Changed 13 years ago by Schusch

well - a tick box would be a nice idea ...

comment:14 Changed 13 years ago by stoecker

Status: reopenednew

comment:15 Changed 12 years ago by Schusch

Resolution: fixed
Status: newclosed

I think we can close this report, because the interface changed (thanks :-) - it is now possible to give a source for all entities uploaded - so one can upload the things from each source together (but see #4181 for an even better interface)

Modify Ticket

Change Properties
Set your email in Preferences
Action
as closed The owner will remain framm.
as The resolution will be set.
The resolution will be deleted.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.