Re: [dspace-tech] AIP not import all subcommunities, colections and items from export

[helix84]

What command did you use for exporting the community? During the export,
you should have gotten one commun...@123456789-2.zip file, a bunch
of COLLECTION@123456789-*.zip and ITEM@123456789-*.zip files. Were they
created? Did you copy them all over to the target? It seems to me that you
copied just the commun...@123456789-2.zip file.


Regards,
~~helix84

Compulsory reading: DSpace Mailing List Etiquette
https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette

-- 
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.

Re: [dspace-tech] AIP not import all subcommunities, colections and items from export

[Claudia Jürgen]

Hi Christian,

can you determine which objects are missing and are there any error in the logs.
I haven't used the submit mode  (-s) only the restore mode (-r) which worked 
fine for a hierarchy.
Maybe you had mapped items and in combination with -o skipIfParentMissing=true 
this might cause problems:
"When an Item is mapped to one or more Collections, this mapping is recorded in the 
AIP using the mapped Collection's handle. Unfortunately, since the submission mode (-s) 
assigns new handles to all objects in the hierarchy, this may mean that the mapped 
Collection's handle will have changed (or even that a different Collection will be 
available at the original mapped Collection's handle). "
see 
https://wiki.duraspace.org/display/DSDOC5x/AIP+Backup+and+Restore#AIPBackupandRestore-SubmittinganAIPHierarchy
Furthermore if you did not disable workflows (-w) items might still be in 
workflows.

Hope this helps

Claudia Jürgen




Am 28.07.2016 um 00:42 schrieb christian criollo:

Hi all

recently I used the tool AIP to export a community of my repository toward
other repository that create, the problem is when I import the community in
my other instance I suppose that it import all subcommunity , colections
and items but it is not like that, the command that executed is this: /
dspace packager -s -a -t AIP  -e-p 123456789/2  -o
skipIfParentMissing=true  
C:\dspace\bibdigital\exports\Artes-Letra-Diseño\aip1970
what is the error?
thanks for the help




--
Claudia Juergen
Eldorado

Technische Universität Dortmund
Universitätsbibliothek
Vogelpothsweg 76
44227 Dortmund

Tel.: +49 231-755 40 43
Fax: +49 231-755 40 32
claudia.juer...@tu-dortmund.de
www.ub.tu-dortmund.de

Wichtiger Hinweis: Die Information in dieser E-Mail ist vertraulich. Sie ist 
ausschließlich für den Adressaten bestimmt. Sollten Sie nicht der für diese 
E-Mail bestimmte Adressat sein, unterrichten Sie bitte den Absender und 
vernichten Sie diese Mail. Vielen Dank.
Unbeschadet der Korrespondenz per E-Mail, sind unsere Erklärungen 
ausschließlich final rechtsverbindlich, wenn sie in herkömmlicher Schriftform 
(mit eigenhändiger Unterschrift) oder durch Übermittlung eines solchen 
Schriftstücks per Telefax erfolgen.

Important note: The information included in this e-mail is confidential. It is 
solely intended for the recipient. If you are not the intended recipient of 
this e-mail please contact the sender and delete this message. Thank you. 
Without prejudice of e-mail correspondence, our statements are only legally 
binding when they are made in the conventional written form (with personal 
signature) or when such documents are sent by fax.

--
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] Wordpress and Dspace

[Keith Jones]

Hi All,

I was wondering if anyone has worked with pulling information from
dspace(metadata) and presenting it in Wordpress.

I've looked at using the rest api, and possible using the mets file. Any
thoughts or information would be greatly appreciated.

Thanks
Keith

-- 
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] Re: AIP not import all subcommunities, colections and items from export

[christian criollo]

Hi helix

the command that used to export is the next 
/home/dspace-5.5/bibdigital/exports/Artes-Letra-Diseño> 
/home/dspace-5.5/bibdigital/bin/dspace packager -d -a -t AIP -e 
 -i 10906/1970 aip1970.zip and the community, colections and 
items were created and copy all structure of files.


El miércoles, 27 de julio de 2016, 17:42:26 (UTC-5), christian criollo 
escribió:
>
> Hi all
>
> recently I used the tool AIP to export a community of my repository toward 
> other repository that create, the problem is when I import the community in 
> my other instance I suppose that it import all subcommunity , colections 
> and items but it is not like that, the command that executed is this: / 
> dspace packager -s -a -t AIP  -e-p 123456789/2  -o 
> skipIfParentMissing=true  
> C:\dspace\bibdigital\exports\Artes-Letra-Diseño\aip1970 
> what is the error?
> thanks for the help
>
>

-- 
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] Re: AIP not import all subcommunities, colections and items from export

[christian criollo]

Hi Claudia

Thanks for the help I executed with the mode restore and working import all 
structure AIP keep the handle my question is if the new repository has a 
new handle how I can change the handle of item to that redirect new handle 
thanks for the help.

El miércoles, 27 de julio de 2016, 17:42:26 (UTC-5), christian criollo 
escribió:
>
> Hi all
>
> recently I used the tool AIP to export a community of my repository toward 
> other repository that create, the problem is when I import the community in 
> my other instance I suppose that it import all subcommunity , colections 
> and items but it is not like that, the command that executed is this: / 
> dspace packager -s -a -t AIP  -e-p 123456789/2  -o 
> skipIfParentMissing=true  
> C:\dspace\bibdigital\exports\Artes-Letra-Diseño\aip1970 
> what is the error?
> thanks for the help
>
>

-- 
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] DSpace and Google Scholar

[Monika Mevenkamp]

> We are about ready to start a new repository and I want to make sure I am 
> staying on the good side of GoogleScholar
> We are about to bring up a new repository which will make previously 
> published articles, metadata and fulltext pdfs available to the big wide open 
> web. We do want GoogleScholar to happily crawl this new instance. I checked 
> on the Google’s indexing guidelines 
>  and looked at 
> an example item page in our current test instance to figure out whether the 
> instance will be compliant.
> 
> For reference I include the item metadata as well as the generated meta_tags 
> at the end of this message.
> 
> My first observation, there is a mix of citation_* and dcterms and dc 
> metatags in the HTML. The dcterms tags are a bit mysterious, since the item I 
> tested has no dcterms metadata values. Does the metatag generator somehow 
> prefer dcterms for some metadata fields ?
> 
> 
> Here now the Google Scholar requirements that may pose an issue:
> 
> Google*) The publication date tag, e.g., citation_publication_date or 
> DC.issued, must contain the date of publication, i.e., the date that would 
> normally be cited in references to this paper from other papers. Don't use it 
> for the date of entry into the repository - that should go into 
> citation_online_date instead. Provide full dates in the "2010/5/12" format if 
> available; or a year alone otherwise. This tag is required for inclusion in 
> Google Scholar.
> 
> there is a dcterms.issued but not a dc.issued; that looks like a potential 
> problem to me
> 
> in addition we decided to store the electronic issue date in the dc.eissued 
> field, in the absence of dc.issued date we end up with no issue date in meta 
> tags; 
> is there an easy way to fix this - short of storing all issue dates in 
> dc.date.issued ?
> 
> Google*) For journal and conference papers, provide the remaining 
> bibliographic citation data in the following tags: citation_journal_title or 
> citation_conference_title, citation_issn, citation_isbn, citation_volume, 
> citation_issue, citation_firstpage, and citation_lastpage. Dublin Core 
> equivalents are DC.relation.ispartof for journal and conference titles and 
> the non-standard tags DC.citation.volume, DC.citation.issue, 
> DC.citation.spage (start page), and DC.citation.epage (end page) for the 
> remaining fields. Regardless of the scheme chosen, these fields must contain 
> sufficient information to identify a reference to this paper from another 
> document, which is normally all of: (a) journal or conference name, (b) 
> volume and issue numbers, if applicable, and (c) the number of the first page 
> of the paper in the volume (or issue) in question.
> 
> now this may be  problematic
> the items dc.identifier.citation   shows as the DCTERMS.bibliographicCitation
> the journal is listed in the tag DCTERMS.isPartOf
> 
> for ISBNs we decide  to store values in dc.identifier.isbn10 and isbn13 - 
> again: is there an easy way to make these appear in the right metatag ?
> 
> 
> Google*) The author tag, e.g., citation_author or DC.creator, must contain 
> the authors (and only the actual authors) of the paper. Don't use it for the 
> author of the website or for contributors other than authors, e.g., thesis 
> advisors. Author names can be listed either as "Smith, John" or as "John 
> Smith". Put each author name in a separate tag and omit all affiliations, 
> degrees, certifications, etc., from this field. At least one author tag is 
> required for inclusion in Google Scholar.
> 
> there is both dc.contributor.author and a citation_author field
> GoogleScholar shouldn’t complain about having both .. but .. just checking 
> 
> Lots of questions - hoping for answers …  
> 
> Monika
> 
> ---
> 
> dc.contributor.author   Uppaluri, Sravanti
> dc.contributor.author   Brangwynne, Clifford P
> dc.date.accessioned 2016-07-28T19:25:55Z-
> dc.date.available   2016-07-28T19:25:55Z
> dc.date.issued  2015-08-22
> dc.identifier.citation  "A size threshold governs Caenorhabditis elegans 
> developmental progression" Proceedings of the Royal Society B: Biological 
> Sciences, (1813), 282, 20151283 - 20151283, doi:10.1098/rspb.2015.1283
> dc.identifier.issn  0962-8452
> dc.identifier.uri   http://arks.princeton.edu/ark:/9/fk4x06br14 
>  -
> dc.format.extent20151283 - 20151283
> dc.relation.ispartofProceedings of the Royal Society B: Biological 
> Sciences
> dc.titleA size threshold governs Caenorhabditis elegans 
> developmental progression
> dc.type Journal Article
> dc.identifier.doi   doi:10.1098/rspb.2015.1283
> dc.date.eissued 2015-08-19
> dc.identifier.eissn 1471-2954
> 
> 
>  xml:lang="en_US <>" />
>  xml:lang="en_US <>" />
>  scheme="DCTERMS.W3CDTF <>" />
>  scheme="DCTERMS.W3CDTF <>" />
>  scheme="DCTER

Re: [dspace-tech] DSpace and Google Scholar

[Andrea Schweer]

  
  
Hi Monika,

I don't have time for a detailed response, but it is my
understanding that Scholar takes the citatation_* fields as first
preference. Things like journal/conference name typically need a
little bit of tweaking because there is no standard field in DSpace
for these. You should start with this config file for the mappings:
https://github.com/DSpace/DSpace/blob/master/dspace/config/crosswalks/google-metadata.properties

cheers,
Andrea

On 07/29/2016 09:19 AM, Monika
  Mevenkamp wrote:


  
  
  
  

  

  
We are about ready to
  start a new repository and I want to make sure I am
  staying on the good side of GoogleScholar
We are about to bring
  up a new repository which will make previously
  published articles, metadata and fulltext pdfs
  available to the big wide open web. We do want
  GoogleScholar to happily crawl this new instance. I
  checked on the Google’s indexing guidelines and looked
  at an example item page in our current test instance
  to figure out whether the instance will be compliant.


For reference I
  include the item metadata as well as the generated
  meta_tags at the end of this message.


My first observation,
  there is a mix of citation_* and dcterms and dc
  metatags in the HTML. The dcterms tags are a bit
  mysterious, since the item I tested has no dcterms
  metadata values. Does the metatag generator somehow
  prefer dcterms for some metadata fields ?




Here now the Google
  Scholar requirements that may pose an issue:


Google*)
The publication date tag, e.g.,
citation_publication_date or DC.issued, must contain
the date of publication, i.e., the date that would
normally be cited in references to this paper from
other papers. Don't use it for the date of entry
into the repository - that should go into
citation_online_date instead. Provide full dates in
the "2010/5/12" format if available; or a year alone
otherwise. This tag is required for inclusion in
Google Scholar.


there is a
  dcterms.issued but not a dc.issued; that looks like a
  potential problem to me


in addition we
  decided to store the electronic issue date in the
  dc.eissued field, in the absence of dc.issued date we
  end up with no issue date in meta tags; 
is there an easy way
  to fix this - short of storing all issue dates in
  dc.date.issued ?


Google*)
For journal and conference papers, provide the
remaining bibliographic citation data in the
following tags: citation_journal_title or
citation_conference_title, citation_issn,
citation_isbn, citation_volume, citation_issue,
citation_firstpage, and citation_lastpage. Dublin
Core equivalents are DC.relation.ispartof for
journal and conference titles and the non-standard
tags DC.citation.volume, DC.citation.issue,
DC.citation.spage (start page), and
DC.citation.epage (end page) for the remaining
fields. Regardless of the scheme chosen, these
fields must contain sufficient information to
identify a reference to this paper from another
document, which is normally all of: (a) journal or
conference name, (b) volume and issue numbers, if
applicable, and (c) the number of the first page of
the paper in the volume (or issue) in question.


now this may be 
  problematic
the items
  dc.identifier.citation   shows as the
  DCTERMS.bibliographicCitation
the journal is listed
  in the tag DCTERMS.isPartOf

[dspace-tech] Internal System Error on dspace 5.2

[Emmanuel Wilson]

Hello all,

i am facing internal system error while soing metadata-import. Now even i
cannot create a new collection or edit the existing item.

Please see the error log:
* 1st error*
2016-07-29 10:02:41,878 ERROR org.dspace.storage.rdbms.DatabaseManager @
SQL create Error -
org.postgresql.util.PSQLException: ERROR: duplicate key value violates
unique constraint "webapp_pkey"
  Detail: Key (webapp_id)=(12) already exists.
at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2103)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1836)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:512)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:388)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:273)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at
org.dspace.storage.rdbms.DatabaseManager.doInsertPostgres(DatabaseManager.java:1743)
at
org.dspace.storage.rdbms.DatabaseManager.insert(DatabaseManager.java:711)
at
org.dspace.storage.rdbms.DatabaseManager.create(DatabaseManager.java:476)
at
org.dspace.app.util.AbstractDSpaceWebapp.register(AbstractDSpaceWebapp.java:80)
at
org.dspace.app.util.DSpaceContextListener.contextInitialized(DSpaceContextListener.java:128)
at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:5027)
at
org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5525)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
at
org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:745)
















































*2nd error2016-07-29 10:30:52,482 WARN
org.dspace.app.webui.servlet.DSpaceServlet @
dspace@localhost:session_id=C7C8E09E87658CA1D659C4C0C5255EB0:ip_addr=0:0:0:0:0:0:0:1:database_error:org.postgresql.util.PSQLException\colon;
ERROR\colon; duplicate key value violates unique constraint
"metadatavalue_pkey"  Detail\colon; Key (metadata_value_id)=(125069)
already exists.org.postgresql.util.PSQLException: ERROR: duplicate key
value violates unique constraint "metadatavalue_pkey"  Detail: Key
(metadata_value_id)=(125069) already exists.at
org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2103)
at
org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1836)
at
org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:257)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.execute(AbstractJdbc2Statement.java:512)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeWithFlags(AbstractJdbc2Statement.java:388)
at
org.postgresql.jdbc2.AbstractJdbc2Statement.executeQuery(AbstractJdbc2Statement.java:273)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at
org.apache.commons.dbcp.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:96)
at
org.dspace.storage.rdbms.DatabaseManager.doInsertPostgres(DatabaseManager.java:1743)
at
org.dspace.storage.rdbms.DatabaseManager.insert(DatabaseManager.java:711)
at org.dspace.content.MetadataValue.create(MetadataValue.java:293)at
org.dspace.content.DSpaceObject.updateMetadata(DSpaceObject.java:256)at
org.dspace.content.Bitstream.update(Bitstream.java:502)at
org.dspace.app.webui.servlet.admin.EditItemServlet.processUpdateItem(EditItemServlet.java:752)
at
org.dspace.app.webui.servlet.admin.EditItemServlet.doDSPost(EditItemServlet.java:231)
at
org.dspace.app.webui.servlet.DSpaceServlet.processRequest(DSpaceServlet.java:115)
at
org.dspace.app.webui.servlet.DSpaceServlet.doPost(DSpaceServlet.java:73)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:646)at
javax.servlet.http.HttpServlet.service(HttpServlet.java:727)at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
at
org.dspace.app.webui.filter.Registe