[dspace-tech] Re: Problem in Item Submission

2018-11-29 Thread Kiszely András 
Hi, same problem, but i have a not fresh installed dspace 6.3.
I'm sure that config is OK, i did submit before and nothing has been 
changed since.

:O

Regards
A.

2018. november 28., szerda 5:05:02 UTC+1 időpontban 
anjana...@paruluniversity.ac.in a következőt írta:
>
> My problem is : I am facing a problem in Item Submission Process. In this 
> process, when we uploading a file (File Form is PDF) and press the  Next 
> Button,  instead of Review Step , the below message is showing:
>
> *No such file or directory*
>
> Go to DSpace home 
>
> Please contact the site administrator if you wish to report this error. If 
> possible, please provide details about what you were doing at the time this 
> error occurred.
>
> Contact site administrator  || 
> Show 
> underlying error stack 
> 
>
>  
>
> *Java stacktrace: *
>
> java.io.IOException: No such file or directory
>
> at java.io.UnixFileSystem.createFileExclusively(Native Method)
>
> at java.io.File.createNewFile(File.java:1012)
>
> at 
> edu.sdsc.grid.io.local.LocalFile.createNewFile(LocalFile.java:486)
>
> at 
> org.dspace.storage.bitstore.BitstreamStorageManager.store(BitstreamStorageManager.java:300)
>
> at org.dspace.content.Bitstream.create(Bitstream.java:204)
>
> at org.dspace.content.Bundle.createBitstream(Bundle.java:384)
>
> at org.dspace.content.Item.createSingleBitstream(Item.java:895)
>
> at 
> org.dspace.submit.step.UploadStep.processUploadFile(UploadStep.java:502)
>
> at 
> org.dspace.submit.step.UploadStep.doProcessing(UploadStep.java:145)
>
> at sun.reflect.GeneratedMethodAccessor197.invoke(Unknown 
> Source)
>
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
>
> at java.lang.reflect.Method.invoke(Method.java:497)
>
> at org.mozilla.javascript.MemberBox.invoke(MemberBox.java:155)
>
> at 
> org.mozilla.javascript.NativeJavaMethod.call(NativeJavaMethod.java:243)
>
> at 
> org.mozilla.javascript.Interpreter.interpretLoop(Interpreter.java:3237)
>
> at 
> org.mozilla.javascript.Interpreter.interpret(Interpreter.java:2394)
>
> at 
> org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:162)
>
> at 
> org.mozilla.javascript.ContextFactory.doTopCall(ContextFactory.java:393)
>
> at 
> org.mozilla.javascript.ScriptRuntime.doTopCall(ScriptRuntime.java:2834)
>
> at 
> org.mozilla.javascript.InterpretedFunction.call(InterpretedFunction.java:160)
>
> at org.mozilla.javascript.Context.call(Context.java:538)
>
> at 
> org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1833)
>
> at 
> org.mozilla.javascript.ScriptableObject.callMethod(ScriptableObject.java:1803)
>
> at 
> org.apache.cocoon.components.flow.javascript.fom.FOM_JavaScriptInterpreter.handleContinuation(FOM_JavaScriptInterpreter.java:698)
>
> at 
> org.apache.cocoon.components.treeprocessor.sitemap.CallFunctionNode.invoke(CallFunctionNode.java:94)
>
> at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:55)
>
> at 
> org.apache.cocoon.components.treeprocessor.sitemap.MatchNode.invoke(MatchNode.java:87)
>
> at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
>
> at 
> org.apache.cocoon.components.treeprocessor.sitemap.SelectNode.invoke(SelectNode.java:82)
>
> at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
>
> at 
> org.apache.cocoon.components.treeprocessor.sitemap.PipelineNode.invoke(PipelineNode.java:143)
>
> at 
> org.apache.cocoon.components.treeprocessor.AbstractParentProcessingNode.invokeNodes(AbstractParentProcessingNode.java:78)
>
> at 
> org.apache.cocoon.components.treeprocessor.sitemap.PipelinesNode.invoke(PipelinesNode.java:81)
>
> at 
> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.process(ConcreteTreeProcessor.java:239)
>
> at 
> org.apache.cocoon.components.treeprocessor.ConcreteTreeProcessor.buildPipeline(ConcreteTreeProcessor.java:186)
>
> at 
> org.apache.cocoon.components.treeprocessor.TreeProcessor.buildPipeline(TreeProcessor.java:260)
>
> at 
> org.apache.cocoon.components.treeprocessor.sitemap.MountNode.invoke(MountNode.java:107)
>
> at 
>

[dspace-tech] Re: OAI-PMH harvest from external system to DSpace collection

2018-11-28 Thread Kiszely András 
Up.
Me and others are fighting with the same problem
Did u find any answer?

2018. március 29., csütörtök 11:42:57 UTC+2 időpontban Jakub Řihák a 
következőt írta:
>
> Hello everyone,
>
> I am trying to set a DSpace collection Content source to be a OAI-PMH set 
> from external system. I would like to harvest metadata of all items in the 
> external OAI-PMH set and use custom made crosswalk to "map" metadata from 
> external OAI set to metadata format defined in our DSpace instance.
>
> According to documentation for DSpace 5, there is the following  OAI 
> harvester configuration option in oai.cfg file:
>
> harvester.oai.metadataformats.PluginName
>
>  
>
>>  
>
>
>> This field can be repeated and serves as a link between the metadata 
>> formats supported by the local repository and those supported by the remote 
>> OAI-PMH provider. It follows the form 
>> harvester.oai.metadataformats.PluginName 
>> = NamespaceURI,Optional Display Name . The pluginName designates the 
>> metadata schemas that the harvester "knows" the local DSpace repository can 
>> support. Consequently, the PluginName must correspond to a previously 
>> declared ingestion crosswalk. The namespace value is used during 
>> negotiation with the remote OAI-PMH provider, matching it against a list 
>> returned by the ListMetadataFormats request, and resolving it to whatever 
>> metadataPrefix the remote provider has assigned to that namespace. Finally, 
>> the optional display name is the string that will be displayed to the user 
>> when setting up a collection for harvesting. If omitted, the 
>> PluginName:NamespaceURI combo will be displayed instead.
>
>
>
> There is the following advice: 
>
>>  Consequently, the PluginName must correspond to a previously declared 
>> ingestion crosswalk.
>
>
> I was trying to find how exactly i should declare new crosswalk, but found 
> nothing comprehensive so far. Does anyone have some experience with 
> defining a declaring new OAI ingest crosswalk?
>
> The idea behind this is to be able to "parse" as much information from 
> external OAI set as possible. When using standard Simple Dublin Core 
> Metadata Format (setting collection to have external content source in Edit 
> collection -> Content source  and then selecting Simple Dublin Core from 
> Metadata format list in setup form), we are only able to parse a very 
> limited amount of information from the external OAI-PMH set.
>
> I was trying to set up a new OAI metadata format (as described in OAI-PMH 
> dissemination) and reference this new OAI metadata format in oai.cfg, but 
> it didn't work. So far it seems hardly the same as OAI-PMH ingestion 
> metadata format, as I understand it.
>
> We are running DSpace 5.6 with XMLUI. 
>
> Thank you for any advice or suggestion,
> with best regards,
>
> Jakub Řihák
>
> Charles University, Central Library
>

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.

[dspace-tech] Import collection file use error?

2018-11-09 Thread Kiszely András 
Hello,

i would like to import some titles into my dspace.
My collections:

123456789/1
bb2ac084-c526-4ef7-812e-df1cceacc137
Folyóiratok

123456789/2
39d84649-70ec-40a3-bb7a-a11083b62757
Arcanum


dtk/12
799c4d08-5bc4-4082-815f-73f244a216de
Második folyóirat


dtk/13
4d5a9485-f3e3-45c0-907f-f72db31722ff
újkollekcijó



I created a file structure for Simple Archive Format and i have a 
collection file with this content:
dtk/13

I tried to import by this command:
root@dspace:/dspace/bin# ./dspace import --add --eperson=myusername.hu 
--source=/tananyag/feltoltesre_var/archive_directory  --mapfile=mapfile141
No collections given. Assuming 'collections' file inside item directory
Adding items from directory: /tananyag/feltoltesre_var/archive_directory
Generating mapfile: mapfile141
Processing collections file: collections
Cannot resolve dtk/13 to a collection. Skipping.
Started: 1541766694907
Ended: 1541766697583
Elapsed time: 2 secs (2676 msecs)

And later by this:
root@dspace:/dspace/bin# ./dspace import --add --eperson=myusername.hu 
--source=/tananyag/feltoltesre_var/archive_directory  --mapfile=mapfile14 
--collection=dtk/13
Destination collections:
Owning  Collection: újkollekcijó
Adding items from directory: /tananyag/feltoltesre_var/archive_directory
Generating mapfile: mapfile14
Adding item from directory item_016
Loading dublin core from 
/tananyag/feltoltesre_var/archive_directory/item_016/dublin_core.xml
Schema: dc Element: language Qualifier:  Value: hu_HU
Schema: dc Element: coverage Qualifier:  Value: 2001 - 2004
Schema: dc Element: rights Qualifier:  Value: Jogos.
Loading dublin core from 
/tananyag/feltoltesre_var/archive_directory/item_016/metadata_dtk.xml
Schema: dtk Element: subtitle Qualifier:  Value:
Schema: dtk Element: player Qualifier:  Value: pdfplayer
Processing contents file: 
/tananyag/feltoltesre_var/archive_directory/item_016/contents
Bitstream: patik_lukovics_imreh.pdf
Bitstream: kovasz_kii_tanulm.pdf
Processing handle file: handle
It appears there is no handle file -- generating one
0 item_016
Started: 1541766595661
Ended: 1541766599738
Elapsed time: 4 secs (4077 msecs)

I think the first one should be fine too, but it isn't .
Any idea?
(I have more thousand items for import but varied collections.)

Regards, Andras

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-tech+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-tech@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.