[Dspace-devel] item submission text area
hi all, -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] item submission text area
hi all, iam working on mankin and would like to remove the text area for desription when one is submiting an item and add my own editor.anyonee know how to do this? thanks -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Dspace-devel Digest, Vol 37, Issue 20
Hi Larry, I am afraid we did not discussed at all specifications, architecture and finally implementation strategy. I sent you a rather detailed functional description of what I have already implemented: http://www.windmusic.org/dspace but I received no answer or comment on this document by anyone before you announce a partial implementation on your side. My implementation is not touching database structure as it relies mostly on Lucene. I will pursue my documentation effort as implementation chores are leaving me more and more time for that. This documentation will be soon disclosed to DSpace community. My next implementation step will be for Belgium Poison Centre where faceted browsing is a must have addition to what is already done. Still hoping, one day, being coached by a commiter to share results of our work... Christophe Dupriez Date: Fri, 26 Jun 2009 05:22:06 + (UTC) From: Larry Stone (JIRA) a...@dspace.org Subject: [Dspace-devel] [DSpace-JIRA] Created: (DS-236) Authority Control, and plug-in choice control for Metadata Fields To: dspace-devel@lists.sourceforge.net Message-ID: 19550807.1245993726238.javamail.j...@domu-12-31-38-00-78-f1 Content-Type: text/plain; charset=UTF-8 Authority Control, and plug-in choice control for Metadata Fields - Key: DS-236 URL: http://jira.dspace.org/jira/browse/DS-236 Project: DSpace 1.x Issue Type: New Feature Components: DSpace API, XMLUI Affects Versions: 1.6.0 Reporter: Larry Stone Add authority control, and optionally just choice control (i.e. AJAX menus in UI) for metadata fields. See wiki page for details and documentation: http://wiki.dspace.org/index.php/Authority_Control_of_Metadata_Values Source is available on svn branch: http://scm.dspace.org/svn/repo/sandbox/authority-control-1_6-prototype (this jira entry added to complete the DSpace Communications Trifecta) -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [ dspace-Patches-2812680 ] Greek Translation v1.5.2
Patches item #2812680, was opened at 2009-06-26 10:32 Message generated for change (Tracker Item Submitted) made by xsilliga You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=319984aid=2812680group_id=19984 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Xristoforos silligardos (xsilliga) Assigned to: Nobody/Anonymous (nobody) Summary: Greek Translation v1.5.2 Initial Comment: Greek Translation for Dspace 1.5.2 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=319984aid=2812680group_id=19984 -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [ dspace-Patches-2812680 ] Greek Translation v1.5.2
Patches item #2812680, was opened at 2009-06-26 10:32 Message generated for change (Settings changed) made by xsilliga You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=319984aid=2812680group_id=19984 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Closed Resolution: None Priority: 5 Private: No Submitted By: Xristoforos silligardos (xsilliga) Assigned to: Nobody/Anonymous (nobody) Summary: Greek Translation v1.5.2 Initial Comment: Greek Translation for Dspace 1.5.2 -- You can respond by visiting: https://sourceforge.net/tracker/?func=detailatid=319984aid=2812680group_id=19984 -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Updated: (DS-237) Unable to view the items in a web browser that were imported via command line using Batch import function in ver 1.5.2
[ http://jira.dspace.org/jira/browse/DS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Yureshwar updated DS-237: - Attachment: no items after import was done in collection id.jpg You can see the collection id in the address bar after 123456789/ Unable to view the items in a web browser that were imported via command line using Batch import function in ver 1.5.2 -- Key: DS-237 URL: http://jira.dspace.org/jira/browse/DS-237 Project: DSpace 1.x Issue Type: Bug Components: JSPUI, XMLUI Affects Versions: 1.5.1, 1.5.2 Environment: Linux, windows Reporter: Yureshwar Priority: Critical Attachments: Importing files to collection id 2.jpg, no items after import was done in collection id.jpg Original Estimate: 4 days Remaining Estimate: 4 days I am able to do batch import via command line. It does not show any errors. It also creates map file. But in map file there wont be any data. If i want to view those imported items in a web browser i am unable to view. Means there will be no use of doing batch import. The contents of the folder are in the standard format for doing batch import. Like Contents.txt-- filename Dublin_core.xml-- dublin_core dcvalue element=contributor qualifier=authorJohn/dcvalue dcvalue element=language qualifier=isoen/dcvalue dcvalue element=subject qualifier=noneTechnology/dcvalue dcvalue element=title qualifier=noneSample Title/dcvalue /dublin_core filename.ext Even when i have exported some items from the repository and importing the same files into the repository it is not showing at all. I have checked the log files also it doesn't show any errors it shows the following messages. 2009-06-26 14:12:45,060 INFO org.dspace.core.ConfigurationManager @ Loading from classloader: file:/C:/dspace1/config/dspace.cfg 2009-06-26 14:12:45,160 INFO org.dspace.core.ConfigurationManager @ Using dspace provided log configuration (log.init.config) 2009-06-26 14:12:45,160 INFO org.dspace.core.ConfigurationManager @ Loading: /dspace1/config/log4j.properties Regards, Yureshwar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DSpace-JIRA] Resolved: (DS-228) Community Admin XMLUI: Delegated Admins Patch
[ http://jira.dspace.org/jira/browse/DS-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Donohue resolved DS-228. Resolution: Fixed Fix Version/s: 1.6.0 Assignee: Tim Donohue This patch has now been committed to DSpace TRUNK in preparation for DSpace 1.6.0 release. I've also applied the following updates suggested by Andrea Bollini's previous comments: 1) db sql include RESTRICT constraint, I suggest to remove it so to make the change more similar to the other schema decision make in DSpace *This change has been made as suggested.* 2) dspace-api patch use old DatabaseManager method to query (i.e. don't make properly use of prepared statement and parameter binding) *This change has been made as suggested.* 3) deleting of a community should not automatically delete the admin group as we already done with collection This change was *NOT* made for the following reason: The Community should auto-delete its own Administrators Group. The Collection also auto-deletes its own Administrators group. As these two groups are *different* admin groups, both calls are necessary, to ensure that those Administrator groups don't remain in the database even after the Community/Collection was deleted. 4) I have seen that we add to the admin group also other permission (WRITE, ADD) but this should be not necessary *This change has been made as suggested.* Creating a Community Admin should only add the ADMIN permission, and need not add the WRITE or ADD permission (as it was previously). 5) it has been introduced a useful convenience method groupFromColumn in the Community class we should find a more appropriate home for it For now, I've left this groupFromColumn() method on the Community object, as I'm not sure where this is best placed (though I agree with Andrea that it may be best to pull this out into a more appropriate home). Community Admin XMLUI: Delegated Admins Patch -- Key: DS-228 URL: http://jira.dspace.org/jira/browse/DS-228 Project: DSpace 1.x Issue Type: New Feature Components: DSpace API, XMLUI Affects Versions: 1.6.0 Reporter: Tim Donohue Assignee: Tim Donohue Fix For: 1.6.0 Attachments: api-sql-rev1.patch, database_schema_changes.sql, dspace-api.patch, dspace-xmlui-api.patch, dspace-xmlui-webapp.patch This set of patches enables Delegated Administration within the XMLUI. These patches were made against the latest DSpace trunk code (as of 12-Jun-2009) in preparation for DSpace 1.6. WARNING: THESE PATCHES MODIFY THE CORE API OF DSPACE. THEY ALSO MODIFY THE UNDERLYING DATABASE STRUCTURE SLIGHTLY. Essentially, this adds delegated administration capabilities, and allows administrative rights to auto-inherit from Community to Collection to Item to Bundle to Bitstream. (So, if you are a Community Admin, you can also administer any Collection in that Community or any Item owned by those Collections). This now creates three main levels of Admins: * System Admin - same as before, can add/edit/delete anything * Community Admin - Can add/edit anything within a specific Community (including sub-communites, collections, items) * Collection Admin - Can add/edit anything within a specific Collection (including all items) There are a few administrative functions which are limited to SYSTEM ADMINS ONLY: * Delete Communities, Collections or Items * Withdraw / Reinstate items List of tasks a Community Admin can perform: * Can create / edit Community, Sub-Communities, Collections or Items within the Community * Can add/edit/remove Authorizations/Roles for Community, Sub-Communities or Collections * Can move items from one collection to another (must have submit privileges on the destination Collection) * Can create/remove item templates for Collections in that Community * CANNOT delete Communities, Sub-Communities, Collections or Items (also cannot withdraw/reinstate items) * CANNOT change the default read access for Collections List of tasks a Collection Admin can perform: * Can create / edit Collection or Items within that Collection * Can add/edit/remove Authorizations/Roles for that Collection * Can move items from one collection to another (must have submit privileges on the destination Collection) * Can create/remove item templates for that Collection * CANNOT delete Collection or Items within it (also cannot withdraw/reinstate items) * CANNOT change the default read access for Collections There are some additional bug fixes and features in this patch: - Adds ability to Move items between Collections (any Admin can perform) - Item Templates now appear properly in XMLUI - Previously, they looked just like
[Dspace-devel] [DSpace-JIRA] Commented: (DS-237) Unable to view the items in a web browser that were imported via command line using Batch import function in ver 1.5.2
[ http://jira.dspace.org/jira/browse/DS-237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=10366#action_10366 ] Yureshwar commented on DS-237: -- Hi Andrea Bollini, Yes i am sure there is no workflow associated with this collection. Unable to view the items in a web browser that were imported via command line using Batch import function in ver 1.5.2 -- Key: DS-237 URL: http://jira.dspace.org/jira/browse/DS-237 Project: DSpace 1.x Issue Type: Bug Components: JSPUI, XMLUI Affects Versions: 1.5.1, 1.5.2 Environment: Linux, windows Reporter: Yureshwar Priority: Critical Attachments: Importing files to collection id 2.jpg, no items after import was done in collection id.jpg Original Estimate: 4 days Remaining Estimate: 4 days I am able to do batch import via command line. It does not show any errors. It also creates map file. But in map file there wont be any data. If i want to view those imported items in a web browser i am unable to view. Means there will be no use of doing batch import. The contents of the folder are in the standard format for doing batch import. Like Contents.txt-- filename Dublin_core.xml-- dublin_core dcvalue element=contributor qualifier=authorJohn/dcvalue dcvalue element=language qualifier=isoen/dcvalue dcvalue element=subject qualifier=noneTechnology/dcvalue dcvalue element=title qualifier=noneSample Title/dcvalue /dublin_core filename.ext Even when i have exported some items from the repository and importing the same files into the repository it is not showing at all. I have checked the log files also it doesn't show any errors it shows the following messages. 2009-06-26 14:12:45,060 INFO org.dspace.core.ConfigurationManager @ Loading from classloader: file:/C:/dspace1/config/dspace.cfg 2009-06-26 14:12:45,160 INFO org.dspace.core.ConfigurationManager @ Using dspace provided log configuration (log.init.config) 2009-06-26 14:12:45,160 INFO org.dspace.core.ConfigurationManager @ Loading: /dspace1/config/log4j.properties Regards, Yureshwar -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.dspace.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
