Re: [dspace-tech] Error during database migration (upgrading 4.3 to 6.2)
Hi Anthony, It sounds like your institution has had a DSpace for a very long time. The "collectionitemsby" views were used in the very early versions of DSpace (1.x), and was removed around version 1.5 (see also: https://jira.duraspace.org/browse/DS-2678). So, my best guess here is someone didn't perform a past upgrade properly, and these views never were actually removed from your database. Our flyway upgrade process is likely assuming they were already removed, as it will identify your DSpace as being version 4.x (and those views didn't exist even in 4.x). That's why it's throwing the error you are seeing. You can safely remove all of those views, as they are no longer used in DSpace. After removing the views, re-run the database migration (e.g. [dspace]/bin/dspace database migrate), and everything should go smoothly. - Tim On Mon, Jan 22, 2018 at 3:36 PM Anthony Petryk wrote: > Hello, > > I'm trying to upgrade from 4.3 to 6.2. I get the error below when I run > the "dspace database migrate" command. I don't know if the views (in bold) > are supposed to exist or not. > > Any help would be appreciated. > > Anthony > > -- > > Database URL: jdbc:postgresql://localhost:5432/dspace62 > Migrating database to latest version... (Check dspace logs for details) > Migration exception: > java.sql.SQLException: Flyway migration error occurred > at > org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:666) > at > org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:574) > at > org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:222) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:606) > at > org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229) > at > org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81) > Caused by: org.flywaydb.core.internal.dbsupport.FlywaySqlScriptException: > Migration V6.0_2015.03.07__DS-2701_Hibernate_migration.sql failed > - > SQL State : 2BP01 > Error Code : 0 > > > > > > *Message: ERROR: cannot drop table collection2item column > collection_legacy_id because other objects depend on it Detail: view > collectionitemsbyauthor depends on table collection2item column > collection_legacy_idview collectionitemsbydate depends on table > collection2item column collection_legacy_idview > collectionitemsbydateaccession depends on table collection2item column > collection_legacy_idview collectionitemsbysubject depends on table > collection2item column collection_legacy_idview collectionitemsbytitle > depends on table collection2item column collection_legacy_id* > Hint: Use DROP ... CASCADE to drop the dependent objects too. > Location : > org/dspace/storage/rdbms/sqlmigration/postgres/V6.0_2015.03.07__DS-2701_Hibernate_migration.sql > (/opt/dspace/dspace/bin/file:/opt/dspace/dspace/lib/dspace-api-6.3-SNAPSHOT.jar!/org/dspace/storage/rdbms/sqlmigration/postgres/V6.0_2015.03.07__DS-2701_Hibernate_migration.sql) > Line : 143 > Statement : ALTER TABLE Collection2Item DROP COLUMN collection_legacy_id > > at > org.flywaydb.core.internal.dbsupport.SqlScript.execute(SqlScript.java:117) > at > org.flywaydb.core.internal.resolver.sql.SqlMigrationExecutor.execute(SqlMigrationExecutor.java:71) > at > org.flywaydb.core.internal.command.DbMigrate.doMigrate(DbMigrate.java:352) > at > org.flywaydb.core.internal.command.DbMigrate.access$1100(DbMigrate.java:47) > at > org.flywaydb.core.internal.command.DbMigrate$4.doInTransaction(DbMigrate.java:308) > at > org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72) > at > org.flywaydb.core.internal.command.DbMigrate.applyMigration(DbMigrate.java:305) > at > org.flywaydb.core.internal.command.DbMigrate.access$1000(DbMigrate.java:47) > at > org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:230) > at > org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:173) > at > org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72) > at > org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:173) > at org.flywaydb.core.Flyway$1.execute(Flyway.java:959) > at org.flywaydb.core.Flyway$1.execute(Flyway.java:917) > at org.flywaydb.core.Flyway.execute(Flyway.java:1373) > at org.flywaydb.core.Flyway.migrate(Flyway.java:917) > at > org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:655) > ... 8 more >
[dspace-tech] Error during database migration (upgrading 4.3 to 6.2)
Hello, I'm trying to upgrade from 4.3 to 6.2. I get the error below when I run the "dspace database migrate" command. I don't know if the views (in bold) are supposed to exist or not. Any help would be appreciated. Anthony -- Database URL: jdbc:postgresql://localhost:5432/dspace62 Migrating database to latest version... (Check dspace logs for details) Migration exception: java.sql.SQLException: Flyway migration error occurred at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:666) at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:574) at org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:222) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:606) at org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229) at org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81) Caused by: org.flywaydb.core.internal.dbsupport.FlywaySqlScriptException: Migration V6.0_2015.03.07__DS-2701_Hibernate_migration.sql failed - SQL State : 2BP01 Error Code : 0 *Message: ERROR: cannot drop table collection2item column collection_legacy_id because other objects depend on it Detail: view collectionitemsbyauthor depends on table collection2item column collection_legacy_idview collectionitemsbydate depends on table collection2item column collection_legacy_idview collectionitemsbydateaccession depends on table collection2item column collection_legacy_idview collectionitemsbysubject depends on table collection2item column collection_legacy_idview collectionitemsbytitle depends on table collection2item column collection_legacy_id* Hint: Use DROP ... CASCADE to drop the dependent objects too. Location : org/dspace/storage/rdbms/sqlmigration/postgres/V6.0_2015.03.07__DS-2701_Hibernate_migration.sql (/opt/dspace/dspace/bin/file:/opt/dspace/dspace/lib/dspace-api-6.3-SNAPSHOT.jar!/org/dspace/storage/rdbms/sqlmigration/postgres/V6.0_2015.03.07__DS-2701_Hibernate_migration.sql) Line : 143 Statement : ALTER TABLE Collection2Item DROP COLUMN collection_legacy_id at org.flywaydb.core.internal.dbsupport.SqlScript.execute(SqlScript.java:117) at org.flywaydb.core.internal.resolver.sql.SqlMigrationExecutor.execute(SqlMigrationExecutor.java:71) at org.flywaydb.core.internal.command.DbMigrate.doMigrate(DbMigrate.java:352) at org.flywaydb.core.internal.command.DbMigrate.access$1100(DbMigrate.java:47) at org.flywaydb.core.internal.command.DbMigrate$4.doInTransaction(DbMigrate.java:308) at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72) at org.flywaydb.core.internal.command.DbMigrate.applyMigration(DbMigrate.java:305) at org.flywaydb.core.internal.command.DbMigrate.access$1000(DbMigrate.java:47) at org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:230) at org.flywaydb.core.internal.command.DbMigrate$2.doInTransaction(DbMigrate.java:173) at org.flywaydb.core.internal.util.jdbc.TransactionTemplate.execute(TransactionTemplate.java:72) at org.flywaydb.core.internal.command.DbMigrate.migrate(DbMigrate.java:173) at org.flywaydb.core.Flyway$1.execute(Flyway.java:959) at org.flywaydb.core.Flyway$1.execute(Flyway.java:917) at org.flywaydb.core.Flyway.execute(Flyway.java:1373) at org.flywaydb.core.Flyway.migrate(Flyway.java:917) at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.java:655) ... 8 more Caused by: org.postgresql.util.PSQLException: ERROR: cannot drop table collection2item column collection_legacy_id because other objects depend on it Detail: view collectionitemsbyauthor depends on table collection2item column collection_legacy_id view collectionitemsbydate depends on table collection2item column collection_legacy_id view collectionitemsbydateaccession depends on table collection2item column collection_legacy_id view collectionitemsbysubject depends on table collection2item column collection_legacy_id view collectionitemsbytitle depends on table collection2item column collection_legacy_id Hint: Use DROP ... CASCADE to drop the dependent objects too. at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2458) at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2158) at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:291) at org.postgresql.jdbc.PgStatement.executeInternal(PgSta
Re: [dspace-tech] REST API not working
Hi, Hardy: I think I found the problem in the catalina.out log. I see: SEVERE: Error listenerStart SEVERE: Context [/rest] startup failed due to previous errors SEVERE: Exception sending context destroyed event to listener instance of class org.dspace.app.util.DSpaceWebappListener So, for some reason the Rest API is failing. Still not sure why, but I will continue to dig. George On Mon, Jan 22, 2018 at 2:11 PM, Hardy Pottinger wrote: > Hi, George, by any chance are you putting your Tomcat server behind a > reverse proxy? If so, you'll probably want to drop the security constraint > for the REST-API, since you don't need to encrypt traffic between the > reverse proxy and Tomcat. Here's an example of what I mean: > > https://github.com/UCLALibrary/DSpace/pull/18/files > > Now, be careful, do *not* drop that constraint if you're exposing Tomcat > to the world. :-) > > --Hardy > > On Mon, Jan 22, 2018 at 12:30 PM, George Kozak wrote: > >> Hi... >> I wrote about this back on January 8th, but didn't get any replies...so I >> am trying again :-) >> In our DSpace 6.2 installation, if I try to access the REST API, the >> system responds with "Page Not Found" as if I had typed in an inaccurate >> URL. It does this even when I try: >> curl https:///rest/test >> >> In the tomcat server.xml, I have: >> >> >> Does anyone have any ideas why the code would not recognize the REST API? >> (PS: it worked fine in DSpace 5.5) >> Thanks! >> >> -- >> *** >> George Kozak >> Digital Library Specialist >> Cornell University Library - IT >> 218 Olin Library >> Cornell University >> Ithaca, NY 14853 >> 607-255-8924 <(607)%20255-8924> >> g...@cornell.edu >> >> -- >> 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. >> > > -- *** George Kozak Digital Library Specialist Cornell University Library - IT 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 g...@cornell.edu -- 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] Database error when trying to edit epersons (oracle - ORA-00932: inconsistent datatypes: expected -
No database changes have been made for the longest time. Definitely no code changes. I will test in my dev environment tomorrow. I also have a dev DB instance and will play around with combinations and see if there is any pointers. Either way, I'm a bit dead in the water without being able to maintain groups/etc. -Don. On Monday, January 22, 2018 at 2:36:33 PM UTC-5, Tim Donohue wrote: > > Hi Don, > > This error sounds similar to this reported issue: > > https://jira.duraspace.org/browse/DS-3649 > > However, in this situation the error was said to start with version 5.6, > not version 5.5. Looking at the ticket again, it looks like we don't yet > have a solution. But, maybe it'll give you (or others reading this) hints > as to what might be happening. > > - Tim > > On Mon, Jan 22, 2018 at 12:46 PM Donald Bynum > wrote: > >> I am running DSpace 5.5 with XMLUI and Oracle. I have been running just >> fine for a long time. Today I went to add a new collection and edit some >> groups. When I click on Add eperson (or for that matter the eperson link >> on the admin page) I get an Oracle error: >> >> oracle - ORA-00932: inconsistent datatypes: expected - got CLOB >> >> I have no idea what might have changed, given that any changes would have >> been done by me. Guessing that something at the data layer has been >> corrupted in some way. Can anyone provide some insight/assistance. >> >> Best regards, >> >> Don Bynum >> >> -- >> 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...@googlegroups.com . >> To post to this group, send email to dspac...@googlegroups.com >> . >> Visit this group at https://groups.google.com/group/dspace-tech. >> For more options, visit https://groups.google.com/d/optout. >> > > > -- > Tim Donohue > Technical Lead for DSpace & DSpaceDirect > DuraSpace.org | DSpace.org | DSpaceDirect.org > -- 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] REST API not working
Hi, Hardy: Thanks for the suggestion. Yes, our tomcat sits behind a reverse proxy. However, after removing the Security constraint from the web.xml for the Rest API, and restarting tomcat, I still get the same "Page Not Found" error. I'm definitely stumped. George On Mon, Jan 22, 2018 at 2:11 PM, Hardy Pottinger wrote: > Hi, George, by any chance are you putting your Tomcat server behind a > reverse proxy? If so, you'll probably want to drop the security constraint > for the REST-API, since you don't need to encrypt traffic between the > reverse proxy and Tomcat. Here's an example of what I mean: > > https://github.com/UCLALibrary/DSpace/pull/18/files > > Now, be careful, do *not* drop that constraint if you're exposing Tomcat > to the world. :-) > > --Hardy > > On Mon, Jan 22, 2018 at 12:30 PM, George Kozak wrote: > >> Hi... >> I wrote about this back on January 8th, but didn't get any replies...so I >> am trying again :-) >> In our DSpace 6.2 installation, if I try to access the REST API, the >> system responds with "Page Not Found" as if I had typed in an inaccurate >> URL. It does this even when I try: >> curl https:///rest/test >> >> In the tomcat server.xml, I have: >> >> >> Does anyone have any ideas why the code would not recognize the REST API? >> (PS: it worked fine in DSpace 5.5) >> Thanks! >> >> -- >> *** >> George Kozak >> Digital Library Specialist >> Cornell University Library - IT >> 218 Olin Library >> Cornell University >> Ithaca, NY 14853 >> 607-255-8924 <(607)%20255-8924> >> g...@cornell.edu >> >> -- >> 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. >> > > -- *** George Kozak Digital Library Specialist Cornell University Library - IT 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 g...@cornell.edu -- 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] Database error when trying to edit epersons (oracle - ORA-00932: inconsistent datatypes: expected -
Hi Don, This error sounds similar to this reported issue: https://jira.duraspace.org/browse/DS-3649 However, in this situation the error was said to start with version 5.6, not version 5.5. Looking at the ticket again, it looks like we don't yet have a solution. But, maybe it'll give you (or others reading this) hints as to what might be happening. - Tim On Mon, Jan 22, 2018 at 12:46 PM Donald Bynum wrote: > I am running DSpace 5.5 with XMLUI and Oracle. I have been running just > fine for a long time. Today I went to add a new collection and edit some > groups. When I click on Add eperson (or for that matter the eperson link > on the admin page) I get an Oracle error: > > oracle - ORA-00932: inconsistent datatypes: expected - got CLOB > > I have no idea what might have changed, given that any changes would have > been done by me. Guessing that something at the data layer has been > corrupted in some way. Can anyone provide some insight/assistance. > > Best regards, > > Don Bynum > > -- > 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. > -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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] REST API not working
Hi, George, by any chance are you putting your Tomcat server behind a reverse proxy? If so, you'll probably want to drop the security constraint for the REST-API, since you don't need to encrypt traffic between the reverse proxy and Tomcat. Here's an example of what I mean: https://github.com/UCLALibrary/DSpace/pull/18/files Now, be careful, do *not* drop that constraint if you're exposing Tomcat to the world. :-) --Hardy On Mon, Jan 22, 2018 at 12:30 PM, George Kozak wrote: > Hi... > I wrote about this back on January 8th, but didn't get any replies...so I > am trying again :-) > In our DSpace 6.2 installation, if I try to access the REST API, the > system responds with "Page Not Found" as if I had typed in an inaccurate > URL. It does this even when I try: > curl https:///rest/test > > In the tomcat server.xml, I have: > > > Does anyone have any ideas why the code would not recognize the REST API? > (PS: it worked fine in DSpace 5.5) > Thanks! > > -- > *** > George Kozak > Digital Library Specialist > Cornell University Library - IT > 218 Olin Library > Cornell University > Ithaca, NY 14853 > 607-255-8924 <(607)%20255-8924> > g...@cornell.edu > > -- > 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. > -- 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] Database error when trying to edit epersons (oracle - ORA-00932: inconsistent datatypes: expected -
I am running DSpace 5.5 with XMLUI and Oracle. I have been running just fine for a long time. Today I went to add a new collection and edit some groups. When I click on Add eperson (or for that matter the eperson link on the admin page) I get an Oracle error: oracle - ORA-00932: inconsistent datatypes: expected - got CLOB I have no idea what might have changed, given that any changes would have been done by me. Guessing that something at the data layer has been corrupted in some way. Can anyone provide some insight/assistance. Best regards, Don Bynum -- 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] REST API not working
Hi... I wrote about this back on January 8th, but didn't get any replies...so I am trying again :-) In our DSpace 6.2 installation, if I try to access the REST API, the system responds with "Page Not Found" as if I had typed in an inaccurate URL. It does this even when I try: curl https:///rest/test In the tomcat server.xml, I have: Does anyone have any ideas why the code would not recognize the REST API? (PS: it worked fine in DSpace 5.5) Thanks! -- *** George Kozak Digital Library Specialist Cornell University Library - IT 218 Olin Library Cornell University Ithaca, NY 14853 607-255-8924 g...@cornell.edu -- 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] Recent Spam on DSpace Community and Tech Support lists
All, As you may have noticed (unless your spam filter has kindly filtered it all out), we've had spammers attacking the dspace-community and dspace-tech mailing lists several times a week. Despite our attempts to filter out the spam using Google Groups, many messages are still making it through to our list members. Obviously, this is not ideal. So, for the time being, I've turned off self-registration on all DSpace lists. This means that anyone wanting to join one of the DSpace mailing lists will need to be manually approved before they are a list member. And, no one can post to our lists who is not already a member. I don't take this change lightly, and I sincerely hope this will be temporary (until spam attempts die down). If there are any questions/concerns, please do let me know (either privately or on this mailing list). - Tim -- Tim Donohue Technical Lead for DSpace & DSpaceDirect DuraSpace.org | DSpace.org | DSpaceDirect.org -- 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] In 6.2 in REST dc.description.provenance is missing
Thank you Tim,
In the real program I am logging in as admin. But I wanted to check quickly
in the browser what will I get in the program and here
"dc.description.provenance" was missing. Now I know why :)
Thank you again
Evgeni
On Monday, January 22, 2018 at 5:12:54 PM UTC+2, Tim Donohue wrote:
>
> Hi Evgeni,
>
> I'm pretty sure the REST API hides any fields that are in the
> "metadata.hide. " settings in your dspace.cfg (or local.cfg) file. By
> default, "dc.description.provenance" is hidden to anonymous users (in all
> interfaces), as it may contain sensitive or private information (email
> addresses, etc). It is available however from a UI if you are logged in as
> an Administrator or someone with edit metadata rights (as you noted)
>
> It should also be available/visible if you authenticate to the REST API
> first, and then look at the Item metadata while authenticated.
>
> Alternatively, if you want this field to be available in all interfaces,
> you can un-hide it (in all interfaces) by commenting out this line of the
> dspace.cfg:
>
> https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/dspace.cfg#L798
>
> - Tim
>
> On Mon, Jan 22, 2018 at 9:01 AM Evgeni Dimitrov > wrote:
>
>> When I do in xmlui Item Edit/Metadata, then I see
>> dc.description.provenance with a meaningful value.
>>
>> When I enter in the browser
>> .../rest/items/{item UUID}/metadata
>>
>> then there is no dc.description.provenance
>>
>> Is there some easy patch that I could apply to 6.2?
>>
>> --
>> 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...@googlegroups.com .
>> To post to this group, send email to dspac...@googlegroups.com
>> .
>> Visit this group at https://groups.google.com/group/dspace-tech.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
> --
> Tim Donohue
> Technical Lead for DSpace & DSpaceDirect
> DuraSpace.org | DSpace.org | DSpaceDirect.org
>
--
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] Oracle Database version
Here at Princeton I am using Oracle 11.2.0.4. The Database group plans to upgrade to 12.2.0.1. Has anyone experience with this ? Thanks Monika Monika Mevenkamp mo.me...@gmail.com http://mo-meven.tumblr.com/ http://mcmprogramming.com/mo.meven/ -- 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] In 6.2 in REST dc.description.provenance is missing
Hi Evgeni,
I'm pretty sure the REST API hides any fields that are in the
"metadata.hide. " settings in your dspace.cfg (or local.cfg) file. By
default, "dc.description.provenance" is hidden to anonymous users (in all
interfaces), as it may contain sensitive or private information (email
addresses, etc). It is available however from a UI if you are logged in as
an Administrator or someone with edit metadata rights (as you noted)
It should also be available/visible if you authenticate to the REST API
first, and then look at the Item metadata while authenticated.
Alternatively, if you want this field to be available in all interfaces,
you can un-hide it (in all interfaces) by commenting out this line of the
dspace.cfg:
https://github.com/DSpace/DSpace/blob/dspace-6_x/dspace/config/dspace.cfg#L798
- Tim
On Mon, Jan 22, 2018 at 9:01 AM Evgeni Dimitrov
wrote:
> When I do in xmlui Item Edit/Metadata, then I see
> dc.description.provenance with a meaningful value.
>
> When I enter in the browser
> .../rest/items/{item UUID}/metadata
>
> then there is no dc.description.provenance
>
> Is there some easy patch that I could apply to 6.2?
>
> --
> 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.
>
--
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org
--
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] In 6.2 in REST dc.description.provenance is missing
When I do in xmlui Item Edit/Metadata, then I see dc.description.provenance
with a meaningful value.
When I enter in the browser
.../rest/items/{item UUID}/metadata
then there is no dc.description.provenance
Is there some easy patch that I could apply to 6.2?
--
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.
