Re: [dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin
Below is the result of ./dspace database info. Is the ignored DS-2818 registry update what you were referring to as updating the local DSpace registries? Using DSpace installation in: C:\dspace Database Type: postgres Database URL: jdbc:postgresql://localhost:5432/dspace Database Schema: public Database Username: dspace Database Software: PostgreSQL version 9.4.17 Database Driver: PostgreSQL JDBC Driver version 42.2.1 PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.1) ++-+-+-+ | Version| Description | Installed on| State | ++-+-+-+ | 1 | << Flyway Init >> | 2015-06-09 12:16:21 | Baselin | | 1.1| Initial DSpace 1.1 database schema | 2015-06-09 12:16:22 | Success | | 1.2| Upgrade to DSpace 1.2 schema| 2015-06-09 12:16:22 | Success | | 1.3| Upgrade to DSpace 1.3 schema| 2015-06-09 12:16:22 | Success | | 1.3.9 | Drop constraint for DSpace 1 4 schema | 2015-06-09 12:16:23 | Success | | 1.4| Upgrade to DSpace 1.4 schema| 2015-06-09 12:16:23 | Success | | 1.5| Upgrade to DSpace 1.5 schema| 2015-06-09 12:16:23 | Success | | 1.5.9 | Drop constraint for DSpace 1 6 schema | 2015-06-09 12:16:24 | Success | | 1.6| Upgrade to DSpace 1.6 schema| 2015-06-09 12:16:24 | Success | | 1.7| Upgrade to DSpace 1.7 schema| 2015-06-09 12:16:24 | Success | | 1.8| Upgrade to DSpace 1.8 schema| 2015-06-09 12:16:24 | Success | | 3.0| Upgrade to DSpace 3.x schema| 2015-06-09 12:16:24 | Success | | 4.0| Upgrade to DSpace 4.x schema| 2015-06-09 12:16:24 | Success | | 4.9.2015.10.26 | DS-2818 registry update | | Ignored | | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy | 2015-06-09 12:16:24 | Success | | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint| 2015-06-09 12:16:24 | Success | | 5.0.2014.09.26 | DS-1582 Metadata For All Objects| 2015-06-09 12:16:24 | Success | | 5.6.2016.08.23 | DS-3097 | 2019-03-01 12:55:26 | Success | | 5.7.2017.04.11 | DS-3563 Index metadatavalue resource type id column | 2019-03-01 12:55:26 | Success | | 5.7.2017.05.05 | DS 3431 Add Policies for BasicWorkflow | 2019-03-01 12:55:29 | Success | | 6.0.2015.03.06 | DS 2701 Dso Uuid Migration | 2019-03-01 12:55:31 | Success | | 6.0.2015.03.07 | DS-2701 Hibernate migration | 2019-03-01 12:55:31 | Success | | 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration| 2019-03-01 12:57:49 | Success | | 6.0.2016.01.03 | DS-3024 | 2019-03-01 12:57:49 | Success | | 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables | 2019-03-01 12:57:50 | Success | | 6.0.2016.02.25 | DS-3004-slow-searching-as-admin | 2019-03-01 12:57:50 | Success | | 6.0.2016.04.01 | DS-1955 Increase embargo reason | 2019-03-01 12:57:50 | Success | | 6.0.2016.04.04 | DS-3086-OAI-Performance-fix | 2019-03-01 12:57:51 | Success | | 6.0.2016.04.14 | DS-3125-fix-bundle-bitstream-delete-rights | 2019-03-01 12:57:52 | Success | | 6.0.2016.05.10 | DS-3168-fix-requestitem item id column | 2019-03-01 12:57:52 | Success | | 6.0.2016.07.21 | DS-2775 | 2019-03-01 12:57:52 | Success | | 6.0.2016.07.26 | DS-3277 fix handle assignment | 2019-03-01 12:57:52 | Success | | 6.0.2016.08.23 | DS-3097 | 2019-03-01 12:57:52 | Success | | 6.1.2017.01.03 | DS 3431 Add Policies for BasicWorkflow | 2019-03-01 12:57:52 | Success | ++-+-+-+ On Friday, March 1, 2019 at 2:53:00 PM UTC-5, Tim Donohue wrote: > > Hi David, > > That's definitely unexpected. It sounds like your database upgrade > succeeded, but failed to update your local DSpace registries (the Bitstream > Format Registry). This syntax error is very odd, and unfortunately is > nothing I've seen before: > > 2019-03-01 13:09:16,849 WARN > org.hibernate.engine.jdbc.spi.SqlExceptionHelper @ SQL Error: 0, SQLState: > 42601 > 2019-03-01
Re: [dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin
Hi David, That's definitely unexpected. It sounds like your database upgrade succeeded, but failed to update your local DSpace registries (the Bitstream Format Registry). This syntax error is very odd, and unfortunately is nothing I've seen before: 2019-03-01 13:09:16,849 WARN org.hibernate.engine.jdbc.spi.SqlExceptionHelper @ SQL Error: 0, SQLState: 42601 2019-03-01 13:09:16,849 ERROR org.hibernate.engine.jdbc.spi.SqlExceptionHelper @ Batch entry 0 delete from .webapp where webapp_id=396 was aborted: ERROR: syntax error at or near "." Position: 13 Call getNextException to see other errors in the batch. I'm hoping that the primary issue is that your registries didn't update properly. But, you also may want to look back at the logs for the database upgrade itself, to see if any other strange warnings or errors are noted there. If it's a simple registry issue, you should be able to manually update your registries as noted in Step 11 (part "d") of the Upgrade Docs: https://wiki.duraspace.org/display/DSDOC6x/Upgrading+DSpace If that manual update of the registries doesn't work, then I highly suspect some (other) part of the upgrade didn't complete successfully. You should look back at the logs (or try the upgrade again on a test server, closely watching the logs). You also could verify your database is reporting successful upgrades by checking the output of "./dspace database info". I also just found this old email thread that mentioned this same error. The suggestion in that thread was to check your settings for "db.schema" (which for PostgreSQL should be set to "public"): http://dspace.2283337.n4.nabble.com/DSpace6-SQL-Error-td4684728.html Tim On Fri, Mar 1, 2019 at 12:53 PM David Baker wrote: > Thanks, Tim. I deleted the duplicate COLLECTION_29_DEFAULT_READ group and > the migration proceeded past. It now shows all of the migrations as > successful except DS-2818 registry update, which I'm assuming is normal. > > I'm apparently having an issue somewhere else now, though. When I browse > to my repository, I only get a blank white screen. The end of my dspace.log > file is showing a few errors: > > > 2019-03-01 12:57:19,683 INFO > org.dspace.importer.external.service.ImportService @ Loading 1 import > sources. > 2019-03-01 12:57:30,980 INFO org.dspace.core.LoggerServiceImpl @ Using > dspace provided log configuration (log.init.config) > 2019-03-01 12:57:30,996 INFO org.dspace.core.LoggerServiceImpl @ Loading: > C:\dspace/config/log4j.properties > 2019-03-01 12:57:35,058 INFO org.dspace.storage.rdbms.DatabaseUtils @ > Loading Flyway DB migrations from: filesystem:C:\dspace/etc/postgres, > classpath:org.dspace.storage.rdbms.sqlmigration.postgres, > classpath:org.dspace.storage.rdbms.migration > 2019-03-01 12:57:35,449 INFO > org.flywaydb.core.internal.util.VersionPrinter @ Flyway 4.0.3 by Boxfuse > 2019-03-01 12:57:35,621 INFO > org.flywaydb.core.internal.dbsupport.DbSupportFactory @ Database: > jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.4) > 2019-03-01 12:57:49,574 INFO org.flywaydb.core.internal.command.DbMigrate > @ Migrating schema "public" to version 6.0.2015.08.31 - DS 2701 Hibernate > Workflow Migration > 2019-03-01 12:57:49,887 INFO org.flywaydb.core.internal.command.DbMigrate > @ Migrating schema "public" to version 6.0.2016.01.03 - DS-3024 > 2019-03-01 12:57:50,699 INFO org.flywaydb.core.internal.command.DbMigrate > @ Migrating schema "public" to version 6.0.2016.01.26 - DS 2188 Remove DBMS > Browse Tables > 2019-03-01 12:57:50,918 INFO org.flywaydb.core.internal.command.DbMigrate > @ Migrating schema "public" to version 6.0.2016.02.25 - > DS-3004-slow-searching-as-admin > 2019-03-01 12:57:50,949 INFO > org.flywaydb.core.internal.dbsupport.JdbcTemplate @ DB: column "name" of > relation "epersongroup" does not exist, skipping > 2019-03-01 12:57:51,012 INFO org.flywaydb.core.internal.command.DbMigrate > @ Migrating schema "public" to version 6.0.2016.04.01 - DS-1955 Increase > embargo reason > 2019-03-01 12:57:51,090 INFO org.flywaydb.core.internal.command.DbMigrate > @ Migrating schema "public" to version 6.0.2016.04.04 - > DS-3086-OAI-Performance-fix > 2019-03-01 12:57:52,090 INFO org.flywaydb.core.internal.command.DbMigrate > @ Migrating schema "public" to version 6.0.2016.04.14 - > DS-3125-fix-bundle-bitstream-delete-rights > 2019-03-01 12:57:52,418 INFO org.flywaydb.core.internal.command.DbMigrate > @ Migrating schema "public" to version 6.0.2016.05.10 - > DS-3168-fix-requestitem item id column > 2019-03-01 12:57:52,512 INFO org.flywaydb.core.internal.command.DbMigrate > @ Migrating schema "public" to version 6.0.2016.07.21 - DS-2775 > 2019-03-01 12:57:52,605 INFO org.flywaydb.core.internal.command.DbMigrate > @ Migrating schema "public" to version 6.0.2016.07.26 - DS-3277 fix handle > assignment > 2019-03-01 12:57:52,902 INFO org.flywaydb.core.internal.command.DbMigrate > @ Migrating schema "public" to version 6.0.2016.08.23 - DS-3097 > 2019-03-01
[dspace-tech] DSpace 5.3 Not loading
Hi All, I'm looking for some help trying to find out why I can not get Dspace version 5.3 to load in tomcat. Right now I have a Centos 7 machine, with Tomcat running through HTTPS. I've check that the connector is working between httpds and tomcat because tomcats start-up page is viewable. I've downloaded the 5.3 source, compiled it and moved the xmlui interface into the webapps area of tomcat, replacing the ROOT folder content with the xmlui folder content. I've checked the log files and I'm seeing the following error: SEVERE: Exception sending context destroyed event to listener instance of class org.dspace.app.util.DS paceContextListener java.lang.NullPointerException at org.dspace.storage.rdbms.DatabaseManager.delete(DatabaseManager.java:784) at org.dspace.app.util.AbstractDSpaceWebapp.deregister(AbstractDSpaceWebapp.java:98) at org.dspace.app.util.DSpaceContextListener.contextDestroyed(DSpaceContextListener.java:146) at org.apache.catalina.core.StandardContext.listenerStop(StandardContext.java:5165) at org.apache.catalina.core.StandardContext.stopInternal(StandardContext.java:5829) at org.apache.catalina.util.LifecycleBase.stop(LifecycleBase.java:221) at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:149) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:899) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:875) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:652) at org.apache.catalina.startup.HostConfig.deployDirectory(HostConfig.java:1260) at org.apache.catalina.startup.HostConfig$DeployDirectory.run(HostConfig.java:2002) at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624) at java.lang.Thread.run(Thread.java:748) I'm running postgres, check that it is running and that I'm able to connect to the database. Thanks for any help. -- 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.
Re: [dspace-tech] Re: Upgrade 5.3 to 6.3 - Database upgrade error epersongroup DS-3004-slow-searching-as-admin
Thanks, Tim. I deleted the duplicate COLLECTION_29_DEFAULT_READ group and
the migration proceeded past. It now shows all of the migrations as
successful except DS-2818 registry update, which I'm assuming is normal.
I'm apparently having an issue somewhere else now, though. When I browse to
my repository, I only get a blank white screen. The end of my dspace.log
file is showing a few errors:
2019-03-01 12:57:19,683 INFO
org.dspace.importer.external.service.ImportService @ Loading 1 import
sources.
2019-03-01 12:57:30,980 INFO org.dspace.core.LoggerServiceImpl @ Using
dspace provided log configuration (log.init.config)
2019-03-01 12:57:30,996 INFO org.dspace.core.LoggerServiceImpl @ Loading:
C:\dspace/config/log4j.properties
2019-03-01 12:57:35,058 INFO org.dspace.storage.rdbms.DatabaseUtils @
Loading Flyway DB migrations from: filesystem:C:\dspace/etc/postgres,
classpath:org.dspace.storage.rdbms.sqlmigration.postgres,
classpath:org.dspace.storage.rdbms.migration
2019-03-01 12:57:35,449 INFO
org.flywaydb.core.internal.util.VersionPrinter @ Flyway 4.0.3 by Boxfuse
2019-03-01 12:57:35,621 INFO
org.flywaydb.core.internal.dbsupport.DbSupportFactory @ Database:
jdbc:postgresql://localhost:5432/dspace (PostgreSQL 9.4)
2019-03-01 12:57:49,574 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.0.2015.08.31 - DS 2701 Hibernate
Workflow Migration
2019-03-01 12:57:49,887 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.0.2016.01.03 - DS-3024
2019-03-01 12:57:50,699 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.0.2016.01.26 - DS 2188 Remove DBMS
Browse Tables
2019-03-01 12:57:50,918 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.0.2016.02.25 -
DS-3004-slow-searching-as-admin
2019-03-01 12:57:50,949 INFO
org.flywaydb.core.internal.dbsupport.JdbcTemplate @ DB: column "name" of
relation "epersongroup" does not exist, skipping
2019-03-01 12:57:51,012 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.0.2016.04.01 - DS-1955 Increase
embargo reason
2019-03-01 12:57:51,090 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.0.2016.04.04 -
DS-3086-OAI-Performance-fix
2019-03-01 12:57:52,090 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.0.2016.04.14 -
DS-3125-fix-bundle-bitstream-delete-rights
2019-03-01 12:57:52,418 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.0.2016.05.10 -
DS-3168-fix-requestitem item id column
2019-03-01 12:57:52,512 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.0.2016.07.21 - DS-2775
2019-03-01 12:57:52,605 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.0.2016.07.26 - DS-3277 fix handle
assignment
2019-03-01 12:57:52,902 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.0.2016.08.23 - DS-3097
2019-03-01 12:57:53,168 INFO org.flywaydb.core.internal.command.DbMigrate
@ Migrating schema "public" to version 6.1.2017.01.03 - DS 3431 Add
Policies for BasicWorkflow
2019-03-01 12:57:53,668 INFO org.flywaydb.core.internal.command.DbMigrate
@ Successfully applied 17 migrations to schema "public" (execution time
02:27.528s).
2019-03-01 12:57:53,715 INFO org.dspace.event.EventServiceImpl @
EventService dispatcher pool initialized
2019-03-01 12:57:54,168 INFO org.hibernate.annotations.common.Version @
HCANN01: Hibernate Commons Annotations {4.0.2.Final}
2019-03-01 12:57:54,262 INFO org.hibernate.Version @ HHH000412: Hibernate
Core {4.2.21.Final}
2019-03-01 12:57:54,277 INFO org.hibernate.cfg.Environment @ HHH000206:
hibernate.properties not found
2019-03-01 12:57:54,277 INFO org.hibernate.cfg.Environment @ HHH21:
Bytecode provider name : javassist
2019-03-01 12:57:54,340 INFO org.hibernate.cfg.Configuration @ HHH44:
Configuring from URL: file:/dspace/config/hibernate.cfg.xml
2019-03-01 12:57:54,605 INFO org.hibernate.cfg.Configuration @ HHH41:
Configured SessionFactory: null
2019-03-01 12:57:55,168 INFO org.hibernate.dialect.Dialect @ HHH000400:
Using dialect:
org.dspace.storage.rdbms.hibernate.postgres.DSpacePostgreSQL82Dialect
2019-03-01 12:57:55,199 INFO
org.hibernate.engine.jdbc.internal.LobCreatorBuilder @ HHH000424: Disabling
contextual LOB creation as createClob() method threw error :
java.lang.reflect.InvocationTargetException
2019-03-01 12:57:55,215 INFO org.hibernate.type.BasicTypeRegistry @
HHH000270: Type registration [pg-uuid] overrides previous :
org.hibernate.type.PostgresUUIDType@7ec8809a
2019-03-01 12:57:55,215 INFO org.hibernate.type.BasicTypeRegistry @
HHH000270: Type registration [java.util.UUID] overrides previous :
Re: [dspace-tech] Embargo Feature Does Not Work
Hello Herminarto, As noted in my previous email, I'd recommend looking at how the embargo is set on the item and checking to see if errors are displayed in your log files (when you set a new embargo). It's possible the date format is a problem, but it's also possible something else is going on here. I'm hoping additional clues can help us (on this list) figure out how to help you. So, again, you might want to look more closely at the "start_date" set on the policy for the embargoed Item. Embargoes in DSpace essentially act as an access policy that doesn't trigger until a particular date has passed. You can see that "start_date" in the Admin Edit Item screens. Here's a guide on where to find this information: https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-ManagingEmbargoesonexistingItems I've just retested this feature on our Demo site ( http://demo.dspace.org/xmlui/), which is also running DSpace 6.3. The date should work under any of those formats (the text there looks to be slightly incorrect). So, the formats , -MM, -MM-DD *and* MM/DD/ are all acceptable date formats. I also verified that if I submit a document on the demo site, and set an embargo date of 03/31/2019 (March 31, 2019), then the embargo takes effect immediately. If I logout and attempt to access the newly embargoed item, then I am sent to a page that says "This item is restricted". Here's the Item that I just submitted and embargoed: http://demo.dspace.org/xmlui/handle/10673/224 If you login as the Demo Administrator (email: dspacedemo+ad...@gmail.com , password: dspace) then you will be able to see that item. But, as an anonymous user, you'll see the "This item is restricted" page. So, I'm not sure exactly what could be happening on your local instance. I'd recommend checking your logs for errors and also verify that the "start_date" is being set to the embargo date on the Item policies. Maybe there will be clues available there that could help us all figure out the problem. Good luck, Tim On Thu, Feb 28, 2019 at 8:34 PM Herminarto Nugroho < herminarto.nugr...@gmail.com> wrote: > Hi Tim, > > Thanks for the reply. > > I am attempting to access the file after logging out (it means I am > anonymous), and still able to access the file. > > Indeed, as an Admin I can modify the access policy of an existing file > such that that particular item can only be accessed after a certain date. > > The problem is when the user wants to submit new files, and decided to set > the embargo feature ON, the embargo feature in the submission process does > not work well. I assume the problem is in the format of the date, but I am > not sure. When I tried to submit a file and set the embargo,the date format > does not match the accepted format. as you can see in the attached figure. > > Then I try to use JSPUI as well. The embargo still does not work, and even > I cannot specify the date at all. > > [image: Screenshot_2.jpg] > Best regards, > > Herminarto > > Pada Kamis, 28 Februari 2019 23.51.37 UTC+7, Tim Donohue menulis: >> >> Hello Herminarto, >> >> I'm not sure if this is the problem, but is it possible that you are >> attempting to access the embargoed item *while you are logged in as an >> Administrator*? >> >> Embargoes should take effect immediately. However, Administrative users >> are *not* subject to those embargoes, and they will still be able to >> download the items while they are logged in. All other logged in users >> (and anonymous users) should not be able to download the item. >> >> If this is not the problem, you might want to look more closely at the >> "start_date" set on the policy for the embargoed Item. Embargoes in DSpace >> essentially act as an access policy that doesn't trigger until a particular >> date has passed. You can see that "start_date" in the Admin Edit Item >> screens. Here's a guide on where to find this information: >> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-ManagingEmbargoesonexistingItems >> >> You also might want to verify in the DSpace logs that no errors are >> occurring when you assign the embargo to a new Item. >> >> Please report back on this mailing list with anything you find or if you >> discover what the problem is. >> >> Thanks, >> >> Tim >> >> >> On Thu, Feb 28, 2019 at 7:24 AM Herminarto Nugroho < >> herminart...@gmail.com> wrote: >> >>> Dear all, >>> >>> I tried to enable the embargo feature by following the instruction from >>> https://wiki.duraspace.org/display/DSDOC6x/Embargo#Embargo-SimpleEmbargoSettings >>> . >>> I am using dspace 6.3 with xmlui. It seems everything's going ok, but >>> when I try to submit a document with embargo, I specified the date the >>> embargo should be lifted long way on the future, my document can still be >>> downloaded freely right after my submission complete (which means the >>> embargo does not work). When I see the column in which I mention embargo >>> until specific date, it seems the date
[dspace-tech] Re: DSpace build Mirage2 issue
I once had an issue similar to this and it was because of the repository of
bower. I had to edit the .bowerrc file and change its content:
vim dspace-xmlui-mirage2/src/main/webapp/.bowerrc
> {
> "directory": "vendor",
> "registry": "https://registry.bower.io;
> }
>
On Friday, March 1, 2019 at 2:01:49 AM UTC-5, Sunita Barve wrote:
>
> Even after building dspace successfully with mirage2 the screen looks like
> attached screen.
>
> Can someone help to solve the issue.
>
>
> with reg
>
> Dr. Sunita Barve
> KRC/Library
> CSIR-NCL, Pune
>
--
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] SOLR Query doesn't coincide with DSpace Item Usage Statistics
Hi! In the usage statistics on DSpace I get a total views of 136 but when I do a Solr Query I get 155. What may I be doing wrong? DSpace Item Usage Statistics: Solr QUERY: select?indent=on=0=type:0+owningItem:c97292cc-d639-4d38-8531-892b3d719138=-isBot:true=statistics_type:view -- 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.
Re: [dspace-tech] I identifying document name using Tables in database
Hello Josiah, can you be more specific about "can not open document in a browser"? If you are at an item you actually have the information already (meaning handle of the item, name of the file) The items in your repositoy are restricted: http://54.171.28.80:8080/jspui/handle/123456789/10885 Only users with the proper rights can view them. Hope this helps Claudia Jürgen Am 01.03.2019 um 08:04 schrieb - Josiah: Dear Team My dspace can not open document in the browser http://54.171.28.80:8080/jspui/ but in the assetstore the files open in bin format I want to how can some one use information in of bitstream table (internal_id) to identify the name of file? is there any relation ship with bitstream table and handle table? because if I know number of handle and internal_id at least i can Identify the name of the document. is there any sql comand to print the table of handle against internal_id Thank you Josiah -- 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. -- 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.
Re: [dspace-tech] Re: ERROR oai import
Hello Freddy, you can query the database: select * from item where in_archive=true and uuid not in (select item_id from item2bundle join metadatavalue on item2bundle.bundle_id=metadatavalue.dspace_object_id where metadata_field_id in (select metadata_field_id from metadatafieldregistry where metadata_schema_id=1 and element='title' and qualifier is null) and text_value='LICENSE'); Did you ever import items, most likely these had no license specified. Hope this helps Claudia Jürgen Am 01.03.2019 um 04:53 schrieb Freddy Guerrero: Thanks Tim for your answer, can someone provide us with a recommendation on how to identify the records that do not contain the license files? Regards El martes, 26 de febrero de 2019, 0:04:39 (UTC-5), Freddy Guerrero escribió: Hi, I use dspace v. 6.3, jspui, and when executing "dspace oai import ", I get this error: java.lang.NullPointerException at org.dspace.storage.bitstore.BitstreamStorageServiceImpl.retr ieve(BitstreamStorageServiceImpl.java:216) at org.dspace.content.BitstreamServiceImpl.retrieve(BitstreamSe rviceImpl.java:309) at org.dspace.xoai.util.ItemUtils.retrieveMetadata(ItemUtils. java:298) at org.dspace.xoai.app.XOAI.index(XOAI.java:421) at org.dspace.xoai.app.XOAI.index(XOAI.java:280) at org.dspace.xoai.app.XOAI.index(XOAI.java:179) at org.dspace.xoai.app.XOAI.index(XOAI.java:145) at org.dspace.xoai.app.XOAI.main(XOAI.java:560) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAcce ssorImpl.java:62) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMe thodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:498) at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptL auncher.java:229) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher. java:81) -- 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. -- 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] I identifying document name using Tables in database
Dear Team My dspace can not open document in the browser http://54.171.28.80:8080/jspui/ but in the assetstore the files open in bin format I want to how can some one use information in of bitstream table (internal_id) to identify the name of file? is there any relation ship with bitstream table and handle table? because if I know number of handle and internal_id at least i can Identify the name of the document. is there any sql comand to print the table of handle against internal_id Thank you Josiah -- 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.
