Hi Mark,

just don't drop the docs in the source code too soon as at some points 
they are more uptodate than the manual. Furthermore there are large 
chunks (submission process) missing in the manual.
In my opinion it would be better to keep the docs (in another format, 
docbook or so) along with the source and populate a manual and other 
material based on this for releases. Docbook would give us the 
opportunity to work on i18n for the documentation.

cheers

Claudia


Mark Diggory schrieb:
> I recommend working with Brad to get this in to their loop. We're  
> getting ready to drop the html documentation in the source and  
> replace it with a PDF export from the Foundations documentation  
> processes.
> 
> -Mark
> 
> On Jul 21, 2008, at 1:04 PM, Tim Donohue wrote:
> 
>> Scott,
>>
>> Touche.. :)  Yea, that's an even better question.  From what I've seen
>> the HTML *seems* the most up-to-date...but, I no longer know what the
>> definitive version is either.
>>
>> So, I'd agree with you.  It'd be nice to have a *definitive* place  
>> where
>> this documentation is going, and a means in which to submit
>> documentation updates (like this one).
>>
>> - Tim
>>
>> Scott Phillips wrote:
>>> Tim,
>>>
>>> That's a great question, what is the "normal" DSpace documentation?
>>> There's the presumably now out of date HTML in the source tree, a  
>>> word /
>>> pdf document floating around, and then the wiki.....
>>>
>>> Scott--
>>>
>>>
>>> On Jul 21, 2008, at 2:00 PM, Tim Donohue wrote:
>>>
>>>> Nice job, Scott (and others who helped)!
>>>>
>>>> Now the obvious question: Can we get this "wrapped up" into the  
>>>> normal
>>>> DSpace Documentation? :)
>>>>
>>>> - Tim
>>>>
>>>> Scott Phillips wrote:
>>>>> DSpacers,
>>>>> It's a funny thing, the DSpace Batch Import Format (of which there
>>>>> are  two) are not documented anywhere other than looking at the
>>>>> source  code. We've run across the situation where a department has
>>>>> some  content to put into the repository and the resources to  
>>>>> create
>>>>> a batch  import, but just don't know how to do it. To solve this
>>>>> problem, we've  created a simple hand out to provide to a  
>>>>> programmer
>>>>> or technical  person in another department or group when they  
>>>>> want to
>>>>> develop their  own batch import script. While it doesn't cover the
>>>>> advanced topics,  like registering bitstreams etc, nor dose it go
>>>>> over the package  importer, it should solve the problem for the  
>>>>> vast
>>>>> majority of cases  where someone needs to create a batch import.
>>>>> I thought this might be useful to others out there, the only other
>>>>> resource on creating batch imports I was able to find is Dorothea's
>>>>> blog:
>>>>> http://cavlec.yarinareth.net/2008/01/07/the-dspace-batch-  
>>>>> importer/.
>>>>> Here is our handout:
>>>>> https://www.tdl.org/documents/DSpaceBatchImportFormat.pdf
>>>>> Scott--
>>>>> ------------------------------------------------------------------- 
>>>>> ------
>>>>>
>>>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>>>> challenge
>>>>> Build the coolest Linux based applications with Moblin SDK & win
>>>>> great prizes
>>>>> Grand prize is a trip for two to an Open Source event anywhere  
>>>>> in the
>>>>> world
>>>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>>>> _______________________________________________
>>>>> DSpace-tech mailing list
>>>>> DSpace-tech@lists.sourceforge.net
>>>>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>>>> -- 
>>>> Tim Donohue
>>>> Research Programmer, Illinois Digital Environment for
>>>> Access to Learning and Scholarship (IDEALS)
>>>> University of Illinois at Urbana-Champaign
>>>> [EMAIL PROTECTED] | (217) 333-4648
>>>
>> -- 
>> Tim Donohue
>> Research Programmer, Illinois Digital Environment for
>> Access to Learning and Scholarship (IDEALS)
>> University of Illinois at Urbana-Champaign
>> [EMAIL PROTECTED] | (217) 333-4648
>>
>> ---------------------------------------------------------------------- 
>> ---
>> This SF.Net email is sponsored by the Moblin Your Move Developer's  
>> challenge
>> Build the coolest Linux based applications with Moblin SDK & win  
>> great prizes
>> Grand prize is a trip for two to an Open Source event anywhere in  
>> the world
>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>> _______________________________________________
>> DSpace-tech mailing list
>> DSpace-tech@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Dspace-devel mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/dspace-devel

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech

Reply via email to