HI Tim
i think i came to know the issue as u mention
see it like this , first we upload a dummy file of the same name as we are
going to upload
this dummy file gives us a handle by which we can access this document
so this this link is put to the actual pdf which calls this file and then we
just replace this file in dspace keeping the same license
this is my gmail id if ur available in gmail please do come online as i can
expalin u in detail
my email id is [email protected]
regards
On Wed, Aug 4, 2010 at 6:51 PM, Tim Donohue <[email protected]> wrote:
> Francis,
>
> Your backup and restore process looks fine, and I don't see any reason why
> it should be changing your database values. You might want to compare your
> database tables before and after the restore -- especially looking at the
> 'handle' table (which stores handles and relates them to
> community/collections/items), and the 'bitstream' table (which is where the
> sequence_id is stored for individual files). These tables should obviously
> not be changing during a normal backup and restore process.
>
> As I've mentioned, if you are actually uploading *new* files or replacing
> existing files, then the Sequence ID *will* change. So, if you are using
> the JSPUI, you'll see your file URLs change in that scenario, as the JSPUI
> creates file URLs like:
> http://demo.dspace.org/jspui/bitstream/10673/4/2/test_pdf.pdf
>
> essentially this translates to:
>
> http://
> [dspace-url]/bitstream/[handle-prefix]/[handle-suffix]/[sequence-id]/[file-name]
>
> (Notice that the sequence-id is included in the URL at all times -- if this
> ID changes, the URL will obviously change)
>
> But, as I mentioned previously the XMLUI has a different URL structure for
> files, that is less reliant on the sequence_id. The XMLUI has a URL
> structure like:
>
>
> http://demo.dspace.org/xmlui/bitstream/handle/10673/4/test_pdf.pdf
>
> essentially this translates to:
>
>
> http://[dspace-url]/bitstream/[handle-prefix]/[handle-suffix]/[file-name]
>
> (In this case, the sequence id is not needed unless you have two files of
> the same name in the same Item -- in which case you can specify it by adding
> "?sequence=#" on the end of the URL)
>
> If this is at all unclear, you can use our Demo Server to browse around a
> sample JSPUI and XMLUI and get a better understanding of these URLs:
> * Demo JSPUI: http://demo.dspace.org/jspui/
> * Demo XMLUI: http://demo.dspace.org/xmlui/
>
> I hope you find this helpful. I still cannot be sure what problems you may
> be running into (as you seem to be doing everything correctly -- unless I'm
> misunderstanding). Perhaps you are still confusing the "sequence_id" and
> the handle? Again, the "sequence_id" may change when new files are uploaded
> to an item (though it shouldn't change during a backup and restore). The
> Handle should never change.
>
> - Tim
>
>
> On 8/4/2010 12:07 AM, فرانسيس Franci$ wrote:
>
> Hi Tim
>>
>> i do the backup in this fashion
>> first i take the dump
>> /usr/local/pgsql/bin/pg_dump dspace > dspace.sql
>> i airchive the assetstore directory
>> on the new machine i first resotre the dump by using this commnad
>> /usr/local/psql/bin/psql -f dspace.sql dspace -h ipaddress
>> as mention on this webiste
>>
>> http://ardb4.ncsi.iisc.ernet.in/dspace/ds_backup.htm#ds
>> please help me
>>
>
--
Regards
Francis Fernandes
A smile is a curve that sets everything straight.....................so Keep
Smiling
------------------------------------------------------------------------------
The Palm PDK Hot Apps Program offers developers who use the
Plug-In Development Kit to bring their C/C++ apps to Palm for a share
of $1 Million in cash or HP Products. Visit us here for more details:
http://p.sf.net/sfu/dev2dev-palm
_______________________________________________
DSpace-tech mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-tech
