Help:How do I organise a bigger research project with a wider team on FactGrid?: Difference between revisions

From FactGrid
Jump to navigation Jump to search
No edit summary
Line 24: Line 24:
* enter contact information on the user page, this can be private information, but this will usually be contact information for your project
* enter contact information on the user page, this can be private information, but this will usually be contact information for your project


Here is a sample for a [[[[User:Julia Mös|user account of a student assistant]]. There are no obstacles to placing your institution's logos on your project pages.
Here is a sample for a [[User:Julia Mös|user account of a student assistant]]. There are no obstacles to placing your institution's logos on your project pages.


== Generate a FactGrid research item for your project ==
== Generate a FactGrid research item for your project ==

Revision as of 12:25, 15 April 2020

back

The extreme transparency of Wikibase instances makes them extremely attractive when organizing teams. You can learn a lot from Wikipedia.

Open your own project space on FactGrid

Wiki installations have various separately searchable namespaces. In the project namespace (all pages that start with "FactGrid:") you should set up your own organizational area for your project. On her you can

  • present your project in more detail
  • link the project staff (direct access facilitates communication with team members)
  • offer exemplary database queries
  • set links to informative subpages of your project

Each page has a discussion page, on which you can clarify problems and find solutions to problems under continuously new headlines.

In coordination, it is practical to use the project pages for information that needs to be considered throughout the project, but to allow direct communication with players through their discussion pages, as changes on their pages generate personal notifications.

Get your own admin account so that you can create accounts for your team members

If you want to coordinate a larger project, let us give you an administrative account with which you can open user accounts in a team. There are conventions in the FactGrid:

  • User accounts are all personal accounts, this also applies to student assistants who “only” enter data.
  • all accounts are kept under real names, where the name is given as at the time of publication according to the model first name (blank) last name.
  • create (and link) a data record for the new user account so that you can use the database yourself in team coordination
  • enter contact information on the user page, this can be private information, but this will usually be contact information for your project

Here is a sample for a user account of a student assistant. There are no obstacles to placing your institution's logos on your project pages.

Generate a FactGrid research item for your project

The FactGrid Research Item is used to bundle data records on which your project is working and to make them citable as project results. More detailed instructions can be found here.

Your employees should ensure that the research item is positioned on all data records into which more project work goes.

Organise Watchlists in your team

Make sure that you and your employees have "watched" all user pages and all project pages. You can find out how to do this here.

On working days, check what changes have occurred on the pages you are watching so that you have questions that are discussed in the project on the screen.

If certain database objects are of great importance to you, set them to observation. In Wikipedia it happens that projects split the observation of central pages in a coordinated manner to ensure that the information levels remain controlled - however, Wikipedia projects are in a delicate position here because anonymous users can change pages coming from outside.

Take the opportunity to share information with colleagues

All data records in the FactGrid can be changed by all registered users of the platform. In the previous work this was an extremely fruitful situation. Colleagues closed gaps in knowledge that their own databases had and gave sources where information was missing.

Act freely and collegially here. Correct information where you find errors easily. Look for an exchange where this becomes exciting. Changes by colleagues are generally interesting and fruitful - but that does not mean that colleagues make mistakes. Take such mistakes, which you can "revert" without formalities, especially as an opportunity to specify your information basis more precisely and to clarify why you are sure to be correct on the specific question.