You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Media uploaded to the database should be manage-able by multiple users for this particular data-type. If someone uploads a photo of a crag, and then a new route is opened or someone comes along who can identify other routes, there should be a structured way to receive this auxiliary contribution.
I would suggest that tags need to be sourced based on who submitted them.
exportinterfaceEntityTag{/** The user who created this tag */owner: MUUID,/** users who want to contest the accuracy of a tag can flag it. this would not be the same as deletion - but could allow us to negatively weight tags by usefulness. A more fine-grained approach would be to have tags rated 0-5 tagRating: { user: MUUID, rating: 0 | 1 | 2 | 3 | 5, }[] */tagContest: MUUID[]}
The text was updated successfully, but these errors were encountered:
I may have to come back and close this issue if I have mis-understood something - but I think tags currently do not have a source?
Media uploaded to the database should be manage-able by multiple users for this particular data-type. If someone uploads a photo of a crag, and then a new route is opened or someone comes along who can identify other routes, there should be a structured way to receive this auxiliary contribution.
I would suggest that tags need to be sourced based on who submitted them.
The text was updated successfully, but these errors were encountered: