Skip to content
This repository has been archived by the owner on Jul 2, 2018. It is now read-only.

Crowd sourcing enablement #1148

Open
natasab opened this issue Jun 29, 2016 · 1 comment
Open

Crowd sourcing enablement #1148

natasab opened this issue Jun 29, 2016 · 1 comment

Comments

@natasab
Copy link

natasab commented Jun 29, 2016

via G.Schelbert, mailing list imeji-community, 18.06.2016

For creating metadata concerning images (a digitized slide library of more than 50.000 items) I would like to have:

  1. (at least) one annotation field which can be edited by everybody (or a particular user group). After a crosscheck by the staff it can be inserted into the regular metadata (as field "notes" e.g.), in order to be part of the searchable metadata (this is crucial - if not searchable, it would not be interesting)

or

  1. (Better:) The possibility to open specified metadata fields to be edited
    by another user group or even everybody (while they still cannot edit the
    rest of the fields).

and

  1. (It would be perfect if) Rules can be added to these (and all) fields,
    such as e.g.: "the string has to be a "Q" plus a number" as it is true for
    Wikidata-IDs.

Having this, one could give things like the following task to a large group of
people: Have a look on the image and the frame! Make a transcription of the
writing on the frame! Identify the object! Search for a correspondig
Wikidata-record and insert its ID!

@natasab
Copy link
Author

natasab commented Jun 29, 2016

First to my mind comes a separate App scenario and database, which has its own workflow and can integrate with imeji via its REST API, as it will be much easier to implement and more flexible to handle, especially in terms of rights management and future features.

After "approval" of the crowd-sourced data, approver can trigger item syncronization with imeji (i.e. the app will push accepted updates to the REST API).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant