[dspace-tech] Modify metadata item display field
I don't want to show the link directly in the field. For example, the Access in http://repository.ust.hk/ir/Record/1783.1-82958 How to show description of link instead of the URL? So when you click the description, it will move to another library/resource Also, I want to move the uploaded file in a field. How to do that? The page currently looks like screenshot below. It has access link and uploaded file in separate field. So I want to make page looks like screenshot below.. The link shows description instead of showing whole address and can download uploaded file in the same field Thank you. Tim -- 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 Database Upgrade[from 1.6 to 6.0] ERROR: cannot drop table metadatavalue column resource_id
After upgraded the dsapce from 1.6.2 to 6.0(ant update) in windows, I tried to upgrade the database, but it exists error in database migration. There is an error. ERROR: cannot drop table metadatavalue column resource_id because other objects depend on it When I drop the column resource_id by using cascade and migrate again, it will say that the column resource_id does not exist. How to solve that problem? The following are the command line(*dspace database info* & *dspace database migrate*) C:\dspace\bin>dspace database info Using DSpace installation in: C:\dspace Database Type: postgres Database URL: jdbc:postgresql://localhost:5433/dspace Database Schema: public Database Username: dspace Database Software: PostgreSQL version 9.6.0 Database Driver: PostgreSQL Native Driver version PostgreSQL 9.4.1212.jre6 PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3) ++--+--- --+-+ | Version| Description | Installed on| State | ++--+--- --+-+ | 1.1| Initial DSpace 1.1 database schema | | Pending | | 1.2| Upgrade to DSpace 1.2 schema | | Pending | | 1.3| Upgrade to DSpace 1.3 schema | | Pending | | 1.3.9 | Drop constraint for DSpace 1 4 schema| | Pending | | 1.4| Upgrade to DSpace 1.4 schema | | Pending | | 1.5| Upgrade to DSpace 1.5 schema | | Pending | | 1.5.9 | Drop constraint for DSpace 1 6 schema| | Pending | | 1.6| Upgrade to DSpace 1.6 schema | | Pending | | 1.7| Upgrade to DSpace 1.7 schema | | Pending | | 1.8| Upgrade to DSpace 1.8 schema | | Pending | | 3.0| Upgrade to DSpace 3.x schema | | Pending | | 4.0| Upgrade to DSpace 4.x schema | | Pending | | 4.9.2015.10.26 | DS-2818 registry update | | Pending | | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy | | Pending | | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint | | Pending | | 5.0.2014.09.26 | DS-1582 Metadata For All Objects | | Pending | | 5.6.2016.08.23 | DS-3097 | | Pending | | 6.0.2015.03.06 | DS 2701 Dso Uuid Migration | | Pending | | 6.0.2015.03.07 | DS-2701 Hibernate migration | | Pending | | 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration | | Pending | | 6.0.2016.01.03 | DS-3024 | | Pending | | 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables| | Pending | | 6.0.2016.02.25 | DS-3004-slow-searching-as-admin | | Pending | | 6.0.2016.04.01 | DS-1955 Increase embargo reason | | Pending | | 6.0.2016.04.04 | DS-3086-OAI-Performance-fix | | Pending | | 6.0.2016.04.14 | DS-3125-fix-bundle-bitstream-delete-rights | | Pending | | 6.0.2016.05.10 | DS-3168-fix-requestitem item id column | | Pending | | 6.0.2016.07.21 | DS-2775 | | Pending | | 6.0.2016.07.26 | DS-3277 fix handle assignment| | Pending | | 6.0.2016.08.23 | DS-3097 | | Pending | ++--+--- --+-+ NOTE: This database is NOT yet initialized for auto-migrations (via Flyway). Your database looks to be compatible with DSpace version 1.6 All upgrades *after* version 1.6 will be run during the next migration. If you'd like to upgrade now, simply run 'dspace database migrate'. C:\dspace\bin>dspace database migrate Using DSpace installation in: C:\dspace Database URL: jdbc:postgresql://localhost:5433/dspace 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.j ava:666) at org.dspace.storage.rdbms.DatabaseUtils.updateDatabase(DatabaseUtils.j ava:574) at org.dspace.storage.rdbms.DatabaseUtils.main(DatabaseUtils.java:222) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.Nat
[dspace-tech] Re: Dspace Database Upgrade[from 1.6 to 6.0] ERROR: cannot drop table metadatavalue column resource_id
There are two views have used the column resource_id, but if they are dropped, there will have another error, and I have no idea how to deal with them:( Tim GD於 2016年11月23日星期三 UTC+8上午10時45分25秒寫道： > > After upgraded the dsapce from 1.6.2 to 6.0(ant update) in windows, I > tried to upgrade the database, but it exists error in database migration. > There is an error. > ERROR: cannot drop table metadatavalue column resource_id because other > objects depend on it > > When I drop the column resource_id by using cascade and migrate again, it > will say that the column resource_id does not exist. > How to solve that problem? > > The following are the command line(*dspace database info* & *dspace > database migrate*) > > C:\dspace\bin>dspace database info > Using DSpace installation in: C:\dspace > > Database Type: postgres > Database URL: jdbc:postgresql://localhost:5433/dspace > Database Schema: public > Database Username: dspace > Database Software: PostgreSQL version 9.6.0 > Database Driver: PostgreSQL Native Driver version PostgreSQL 9.4.1212.jre6 > PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3) > > > ++--+--- > --+-+ > | Version| Description | > Installed > on| State | > > ++--+--- > --+-+ > | 1.1| Initial DSpace 1.1 database schema | > | Pending | > | 1.2| Upgrade to DSpace 1.2 schema | > | Pending | > | 1.3| Upgrade to DSpace 1.3 schema | > | Pending | > | 1.3.9 | Drop constraint for DSpace 1 4 schema| > | Pending | > | 1.4| Upgrade to DSpace 1.4 schema | > | Pending | > | 1.5| Upgrade to DSpace 1.5 schema | > | Pending | > | 1.5.9 | Drop constraint for DSpace 1 6 schema| > | Pending | > | 1.6| Upgrade to DSpace 1.6 schema | > | Pending | > | 1.7| Upgrade to DSpace 1.7 schema | > | Pending | > | 1.8| Upgrade to DSpace 1.8 schema | > | Pending | > | 3.0| Upgrade to DSpace 3.x schema | > | Pending | > | 4.0| Upgrade to DSpace 4.x schema | > | Pending | > | 4.9.2015.10.26 | DS-2818 registry update | > | Pending | > | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy | > | Pending | > | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint | > | Pending | > | 5.0.2014.09.26 | DS-1582 Metadata For All Objects | > | Pending | > | 5.6.2016.08.23 | DS-3097 | > | Pending | > | 6.0.2015.03.06 | DS 2701 Dso Uuid Migration | > | Pending | > | 6.0.2015.03.07 | DS-2701 Hibernate migration | > | Pending | > | 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration | > | Pending | > | 6.0.2016.01.03 | DS-3024 | > | Pending | > | 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables| > | Pending | > | 6.0.2016.02.25 | DS-3004-slow-searching-as-admin | > | Pending | > | 6.0.2016.04.01 | DS-1955 Increase embargo reason | > | Pending | > | 6.0.2016.04.04 | DS-3086-OAI-Performance-fix | > | Pending | > | 6.0.2016.04.14 | DS-3125-fix-bundle-bitstream-delete-rights | > | Pending | > | 6.0.2016.05.10 | DS-3168-fix-requestitem item id column | > | Pending | > | 6.0.2016.07.21 | DS-2775 | > | Pending | > | 6.0.2016.07.26 | DS-3277 fix handle assignment| > | Pending | > | 6.0.2016.08.23 | DS-3097 | > | Pending | > > ++--+--- > --+-+ > > > NOTE: This database is NOT yet initialized for auto-migrations (via > Flyway). > > Your database looks to be compatible with DSpace version 1.6 > All upgrades *after* version 1.6 will be r
[dspace-tech] Re: Dspace Database Upgrade[from 1.6 to 6.0] ERROR: cannot drop table metadatavalue column resource_id
Finally, I modify those two views and it can be done. Tim GD於 2016年11月23日星期三 UTC+8上午10時45分25秒寫道： > > After upgraded the dsapce from 1.6.2 to 6.0(ant update) in windows, I > tried to upgrade the database, but it exists error in database migration. > There is an error. > ERROR: cannot drop table metadatavalue column resource_id because other > objects depend on it > > When I drop the column resource_id by using cascade and migrate again, it > will say that the column resource_id does not exist. > How to solve that problem? > > The following are the command line(*dspace database info* & *dspace > database migrate*) > > C:\dspace\bin>dspace database info > Using DSpace installation in: C:\dspace > > Database Type: postgres > Database URL: jdbc:postgresql://localhost:5433/dspace > Database Schema: public > Database Username: dspace > Database Software: PostgreSQL version 9.6.0 > Database Driver: PostgreSQL Native Driver version PostgreSQL 9.4.1212.jre6 > PostgreSQL 'pgcrypto' extension installed/up-to-date? true (version=1.3) > > > ++--+--- > --+-+ > | Version| Description | > Installed > on| State | > > ++--+--- > --+-+ > | 1.1| Initial DSpace 1.1 database schema | > | Pending | > | 1.2| Upgrade to DSpace 1.2 schema | > | Pending | > | 1.3| Upgrade to DSpace 1.3 schema | > | Pending | > | 1.3.9 | Drop constraint for DSpace 1 4 schema| > | Pending | > | 1.4| Upgrade to DSpace 1.4 schema | > | Pending | > | 1.5| Upgrade to DSpace 1.5 schema | > | Pending | > | 1.5.9 | Drop constraint for DSpace 1 6 schema| > | Pending | > | 1.6| Upgrade to DSpace 1.6 schema | > | Pending | > | 1.7| Upgrade to DSpace 1.7 schema | > | Pending | > | 1.8| Upgrade to DSpace 1.8 schema | > | Pending | > | 3.0| Upgrade to DSpace 3.x schema | > | Pending | > | 4.0| Upgrade to DSpace 4.x schema | > | Pending | > | 4.9.2015.10.26 | DS-2818 registry update | > | Pending | > | 5.0.2014.08.08 | DS-1945 Helpdesk Request a Copy | > | Pending | > | 5.0.2014.09.25 | DS 1582 Metadata For All Objects drop constraint | > | Pending | > | 5.0.2014.09.26 | DS-1582 Metadata For All Objects | > | Pending | > | 5.6.2016.08.23 | DS-3097 | > | Pending | > | 6.0.2015.03.06 | DS 2701 Dso Uuid Migration | > | Pending | > | 6.0.2015.03.07 | DS-2701 Hibernate migration | > | Pending | > | 6.0.2015.08.31 | DS 2701 Hibernate Workflow Migration | > | Pending | > | 6.0.2016.01.03 | DS-3024 | > | Pending | > | 6.0.2016.01.26 | DS 2188 Remove DBMS Browse Tables| > | Pending | > | 6.0.2016.02.25 | DS-3004-slow-searching-as-admin | > | Pending | > | 6.0.2016.04.01 | DS-1955 Increase embargo reason | > | Pending | > | 6.0.2016.04.04 | DS-3086-OAI-Performance-fix | > | Pending | > | 6.0.2016.04.14 | DS-3125-fix-bundle-bitstream-delete-rights | > | Pending | > | 6.0.2016.05.10 | DS-3168-fix-requestitem item id column | > | Pending | > | 6.0.2016.07.21 | DS-2775 | > | Pending | > | 6.0.2016.07.26 | DS-3277 fix handle assignment| > | Pending | > | 6.0.2016.08.23 | DS-3097 | > | Pending | > > ++--+--- > --+-+ > > > NOTE: This database is NOT yet initialized for auto-migrations (via > Flyway). > > Your database looks to be compatible with DSpace version 1.6 > All upgrades *after* version 1.6 will be run during the next migration. > > If you'd like to upgrade now, simply
[dspace-tech] Dspace 6.0 : dspace import issue
This a batch to import item in dspace via simple archive format After upgrading the dspace to 6.0, I changed the "dspace dsrun org.dspace.app.itemimport.ItemImport" to "dspace import" The dspace import command has no error but I cannot find the item in the website. Anyone can help me to solve the problem? Items are in C:\k\temp_import The command input likes the following: C:\dspace\bin>dspace import -a -e [hide_email] -c 10692/145 -s C:/k/temp_imp ort -m mapfile_28496 -w Using DSpace installation in: C:\dspace Destination collections: Owning Collection: DCOM Journal Articles Adding items from directory: C:/k/temp_import Generating mapfile: mapfile_28496 Adding item from directory item_188 Loading dublin core from C:/k/temp_import\item_188\dublin_core.xml Schema: dc Element: type Qualifier: none Value: Journal Articles Schema: dc Element: contributor Qualifier: author Value: Breit, Rhonda Schema: dc Element: contributor Qualifier: author Value: Fitzgerald, Ric hard Schema: dc Element: contributor Qualifier: author Value: Liu, Shuang Schema: dc Element: contributor Qualifier: author Value: Neal, Regan Schema: dc Element: date Qualifier: issued Value: 2017-01-01 00:00:00 Schema: dc Element: title Qualifier: none Value: _28496_How Queensland n ewspapers reported public sector information reform Schema: dc Element: publisher Qualifier: none Value: Schema: dc Element: identifier Qualifier: rdao Value: 28496 Schema: dc Element: subject Qualifier: keywords Value: framing Schema: dc Element: subject Qualifier: keywords Value: Freedom of Inform ation Schema: dc Element: subject Qualifier: keywords Value: journalism Schema: dc Element: subject Qualifier: keywords Value: policy transfer Schema: dc Element: subject Qualifier: keywords Value: reform Schema: dc Element: description Qualifier: abstract Value: How Queenslan d newspapers reported public sector information reform Schema: dc Element: identifier Qualifier: citation Value: Media Internat ional Australia. Vol. No. 162 (1). pp. 90-106. (01/2017). Schema: dc Element: identifier Qualifier: issn Value: ISSN: 1329878X Processing contents file: C:\k\temp_import\item_188\contents Bitstream: 28496_0_Queensland RTI reporting .pdfBundle: ORIGINAL Bitstream: license.txt Bundle: LICENSE 0 item_188 Started: 1486696970960 Ended: 1486696975765 Elapsed time: 4 secs (4805 msecs) Process exitValue: 0 -- 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] Dspace 6.0 : dspace import issue
Hi, Claudia, Thanks for your sugguestions. But I don't know how to make the workflow complete even after watched the dspace wiki. I thought it will do the complete step automatically*.* Claudia Jürgen於 2017年2月15日星期三 UTC+8下午4時14分08秒寫道： > > Hello Tim, > > the "-w" option sends the import through the workflow. So if a workflow > is defined for your collection 10692/145 > > DCOM Journal Articles > > the item will only be visible once the workflow is completed. > > Hope this helps > > Claudia Jürgen > > Am 15.02.2017 um 09:06 schrieb Tim GD: > > This a batch to import item in dspace via simple archive format > > After upgrading the dspace to 6.0, I changed the "dspace dsrun > > org.dspace.app.itemimport.ItemImport" to "dspace import" > > The dspace import command has no error but I cannot find the item in the > > website. > > > > Anyone can help me to solve the problem? > > > > > > Items are in C:\k\temp_import > > The command input likes the following: > > C:\dspace\bin>dspace import -a -e [hide_email] -c 10692/145 -s > C:/k/temp_imp > > ort -m mapfile_28496 -w > > Using DSpace installation in: C:\dspace > > Destination collections: > > Owning Collection: DCOM Journal Articles > > Adding items from directory: C:/k/temp_import > > Generating mapfile: mapfile_28496 > > Adding item from directory item_188 > > Loading dublin core from > C:/k/temp_import\item_188\dublin_core.xml > > Schema: dc Element: type Qualifier: none Value: Journal > Articles > > Schema: dc Element: contributor Qualifier: author Value: Breit, > > Rhonda > > Schema: dc Element: contributor Qualifier: author Value: > > Fitzgerald, Ric > > hard > > Schema: dc Element: contributor Qualifier: author Value: Liu, > Shuang > > Schema: dc Element: contributor Qualifier: author Value: Neal, > Regan > > Schema: dc Element: date Qualifier: issued Value: 2017-01-01 > > 00:00:00 > > Schema: dc Element: title Qualifier: none Value: _28496_How > > Queensland n > > ewspapers reported public sector information reform > > Schema: dc Element: publisher Qualifier: none Value: > > Schema: dc Element: identifier Qualifier: rdao Value: 28496 > > Schema: dc Element: subject Qualifier: keywords Value: framing > > Schema: dc Element: subject Qualifier: keywords Value: Freedom > of > > Inform > > ation > > Schema: dc Element: subject Qualifier: keywords Value: > journalism > > Schema: dc Element: subject Qualifier: keywords Value: policy > > transfer > > Schema: dc Element: subject Qualifier: keywords Value: reform > > Schema: dc Element: description Qualifier: abstract Value: How > > Queenslan > > d newspapers reported public sector information reform > > Schema: dc Element: identifier Qualifier: citation Value: Media > > Internat > > ional Australia. Vol. No. 162 (1). pp. 90-106. (01/2017). > > Schema: dc Element: identifier Qualifier: issn Value: ISSN: > 1329878X > > Processing contents file: C:\k\temp_import\item_188\contents > > Bitstream: 28496_0_Queensland RTI reporting .pdfBundle: > > ORIGINAL > > > > Bitstream: license.txt Bundle: LICENSE > > 0 item_188 > > Started: 1486696970960 > > Ended: 1486696975765 > > Elapsed time: 4 secs (4805 msecs) > > Process exitValue: 0 > > > > > > > > -- > 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...@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-mai
