This is an automated notification sent by LCG Savannah.
It relates to:
task #6974, project CDS Invenio
==============================================================================
LATEST MODIFICATIONS of task #6974:
==============================================================================
Update of task #6974 (project cdsware):
Status: None => Done
Percent Complete: 70% => 100%
Open/Closed: Open => Closed
==============================================================================
OVERVIEW of task #6974:
==============================================================================
URL:
<http://savannah.cern.ch/task/?6974>
Summary: full-text file revision web interface
Project: CDS Invenio
Submitted by: simko
Submitted on: 2008-05-30 15:02
Should Start On: 2008-05-30 00:00
Should be Finished on: 2008-05-30 00:00
Category: WebSubmit
Priority: 7 - High
Status: Done
Privacy: Public
Percent Complete: 100%
Assigned to: jcaffaro
Open/Closed: Closed
Discussion Lock: Any
Effort: 0.00
_______________________________________________________
1) A web interface permitting authors to revise their full-texts is needed.
The web layer of file revision interface would simply gather new information
and call bibdocfile behind the scenes.
2) The same interface could be used by curators or librarians to attach or
otherwise manage full-text files of old records.
3) The full-text management interface should be referenced or interlinked
with the metadata editing interface.
_______________________________________________________
Follow-up Comments:
-------------------------------------------------------
Date: 2008-06-20 13:42 By: Samuele Kaplun <skaplun>
Tony suggests:
--------------------------------------------------------------
1) user chooses a reportNumber, this results
in the recid being written to a file curdir/SN where
you should pick it up. The same function that writes
the recid would also perform checks 'can this user
do this operation?'
2) function sam_1 is called which:
a) allows user to select
- either to replace file and keep previous version
- either to replace file and remove previous version
b) has a 'file input' type field (named e.g. XX) to browse for
the new file. This causes the file to be immediately uploaded
to curdir/files/XX/.
c) displays a list of files for this recid and allows
the user to select which one (and only one) for revision.
3) If the file is to be stamped (depends on the submission)
- function_get_data_for_stamping is called to get the info
for this operation (i.e. other reportnumber,date etc)
- Stamp_Uploaded_Files is called to stamp the file.
4) function sam_2 is called which puts the files correctedly
to storage. The newly input file must be renamed to the
that of the file it replaces. This step (which I think you
would always do anyway) circumvents any possible question
of renaming the file as part of the submission process,
------------------------------------------------------------
_______________________________________________________
Carbon-Copy List:
CC Address | Comment
------------------------------------+-----------------------------
2407 | -UPD-
2195 | -COM-
1576 | -SUB-
==============================================================================
This item URL is:
<http://savannah.cern.ch/task/?6974>
_______________________________________________
Message sent via/by LCG Savannah
http://savannah.cern.ch/
