« 00003 · Edit Form · 00005 »

Summary: Changes to project entry mask

Type

Feature

Raised by

hal

Project

CORE Organic

Related to

Issues?

Date opened

2005–07–05

Priority (1<5)

5

Status

Closed

Assigned to

hal

Hours used

70

Date closed

2005–07–08

Description

A project entry mask (= eprint type) exists. The changes involve the following tasks:

1. Add new fields to the ArchiveMetadataFieldsConfig.pm configuration file
   1. Acronym. Add as TEXT data type.
   2. Project start/stop (month/year). These fields exist, but need to be changed to DATE data types here and in the database, to accommodate both month and year. Use min_resolution=‘month’ or something like this to only include month and not date.
      • For the budget overview we need to calculate the length in months on the basis of these two fields - is this best done in PHP or directly in MySQL (an extra ‘duration’ field is needed in the latter case!?).
   3. Person months. Add as INTEGER.
   4. Budget (in Euro). Now one INTEGER field. Change to three INTEGER fields: International targeted funding, National targeted funding, Other funding.
      • Perhaps add (or keep) total budget field, and perhaps calculate this automatically (see issue 00013.
      • Perhaps add a validation scheme to show these as money numbers (e.g. 3.030.500). Problem: different conventions using either ‘.’ or ‘,’
   5. Homepage/Website. Make new URL field OR change the existing ‘Published online’ to ‘Online’ and use different help texts??
   6. Different help text for the abstract/summary on different eprint types (project, facility, article, book) can be made quite easily. See issue 00014.
   7. Leader. There is already a ‘leader’ field. To get links to contact details in the user records, the leader either has to be the depositor (the present solution) or maybe a link can be created from the leader/author/editor name (see Issues.00003?)
   8. The fields for involved partner institutions, research programmes and their funding agencies will be provided as selections in the affiliation tree. More information on these will be found in the eprint entries that describe them, when these have been uploaded.
2. Add new fields to the database (4 archives + ordervalues)
3. Add those fields that are going to be searchable to the search configuration in ArchiveConfig.pm
4. Add phrases for new fields in phrases-en.xml and phrases-de.xml
5. If requested, it will not be required to upload documents (see 00010)
6. Add new fields to the ‘project’ type in the metadatatypes.xml configuration file
   • This creates the ‘entry mask’ (see below) - the page that users will find when depositing projects
   • Any missing? Order right?
   • Is Document language needed? Seems more fitting for publications.
   • Details on name, website, contact address for Partners/Institutions will be in institution descriptions deposited as individual eprints).
   • The final report / publications (if available) can be attached as document(s) or, better, deposited as a publication eprint and accessed via the Affiliation tree
     • The url to a deposited Final report can also be given in Online context if so desired
     
     
   Project title*
   Translation of title* (preferably english)
   Project acronym
   Project ID number
   
   Project start (month/year)*
   Project end (month/year)*
   Project leader* (link to user record with name, address, phone, fax, e-mail)
   Research institution of the project leader
   Website of the project (url)
   Project budget* (Euro)
   Human resources involved (Person months)
   
   Abstract of projects aims/goals*, materials & methods and (available) results
   Additional abstract (translation)
   (Here we have ‘Document language’ now, but is this needed?)
   Subject areas*
   Keywords
   
   Involved partners / institutions* via Affiliation tree
   Research programme and/or Funding agency* via Affiliation tree
   
   Online context (url)

Implementation of new fields

On Issues.AddedFieldsJuly2005? the technical implementation is described in more detail, covering issues 4, 6, 8 and 9.
Type:

Priority (1<5) =
Status:

Raised by:
Project:
Related to
Date opened:
Assigned to
Hours used (estimates in brackets) =
Date closed:

Description: