In order to assure good metadata qual=
ity, projects using REGISTRY are requested to nominate a chief editor who w=
ill have the following responsibilities:
- Identify and document best practices=
for using REGISTRY and creating metadata in the context of a given project=
and/or institute data policies
- Organize tutorials for editors on a =
regular basis. If wished, the O2A team can upload webminars for speci=
fic projects in our YouTube channel (contact email o2a-support (at) a=
wi.de). In particular, it is crucial that the following issues =
are covered in the tutorials (see best practices=
span>):
- The rationale behind the distinct wo=
rkflow states, in particular de device store
- "Collection" assignment
- "Contact" assignment, in particular =
the role "owner" so that the ownership/affiliation of sensors are assigned =
to the respective institutes. Make sure you request all editors to as=
sign you under role "Editor" as well so that you will be able to perform ac=
tions 5 and 6 below
- "Actions" assignment, in particular =
clarification on which action types trigger the creation of a PID and citat=
ion
- Items for which a version exists (PI=
D + citation listed under "History") can only be moved back to "constructio=
n" state or deleted by REGISTRY administrators (contact email to o2a-suppor=
t (at) awi.de )
<=
/li>
- Remind editors about new functionali=
ty released in REGISTRY . Although software improvements will be post=
ed under "Release Notes" and all editors will be notified via e=
mail, it is crucial that you remind editors of these, in particular in the =
context of your project.
- Periodically control the items creat=
ed and modified by editors within your project/team stored in REGISTRY for =
correctness and completeness and notify editors accordingly
- Move items without a PID back to "co=
nstruction" state, if these do not have adequate metadata. Chie=
f editors are expected to notify the original editor themselves
- Delete "training" items or any other=
which do not belong in the repository. Chief editors are expect=
ed to notify the original editor themselves
Please note that within the framework=
of upcoming projects and integration of existing systems, we will be adapt=
ing and extending the role definition and the best practices accordingly.&n=
bsp; Editors will be notified in due course.