Re: [Dspace-tech] Embargoes in 1.6
Hello Jason, the liftdate is computed based on the embargo terms and the setter used. At the moment there is one default embargo setter: org.dspace.embargo.DefaultEmbargoSetter which assumes the basic use case of the term being a date. Which setter plugin to use is configured in the dspace.cfg: # implementation of embargo setter plugin - replace with local implementation if applicable plugin.single.org.dspace.embargo.EmbargoSetter = org.dspace.embargo.DefaultEmbargoSetter In order to cover other use cases you got to write your own setter and use this instead of the default setter. You can do anything you like, for example using a set of timespans or depend the embargo time on the publication type. This is up to you. Hope that helps Claudia Jürgen Am 31.03.2010 19:59, schrieb Jason Fowler: That makes sense. The only thing I don't understand is how exactly the liftdate is computed. Is that something that happens automatically, or do I need to configure that? Jason Fowler, CA, MSLS From: Claudia Juergen [claudia.juer...@ub.tu-dortmund.de] Sent: Wednesday, March 31, 2010 12:14 PM To: Jason Fowler Cc: claudia.juer...@ub.tu-dortmund.de Subject: RE: [Dspace-tech] Embargoes in 1.6 Hello Jason, only the embargo terms afaik. The liftdate is computed based upon the terms. Claudia Thanks, Claudia! Just one more question. Do I need to add both dc.embargo.terms AND dc.embargo.liftdate to the input-forms.xml? Thanks in advance, Jason Fowler, CA, MSLS attachment: Claudia_Juergen.vcf-- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] Embargoes in 1.6
Hi all, I am testing DSpace 1.6 before we migrate to it. I believe I have the dspace.cfg set up correctly, and I have added dc.embargo.terms and dc.embargo.liftdate to my metadata registry. However, nothing shows up in the submission workflow in any of my xmlui themes, or in jspui. Are there additional changes that I need to make in order to enable this within the workflow? Can someone explain what those are? Thanks, Jason Fowler, CA, MSLS Archives and Special Collections Librarian The Southern Baptist Theological Seminary Vice President, ALABI jfow...@sbts.edu -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Embargoes in 1.6
Hi Jason: One thought: have you added those fields to your input-forms.xml? In other respects, the embargo fields behave just like any other metadata, and can be added to the default set - or any collection-specifc set - of metadata fields used in web submission. The tech doc has instructions on managing input-forms. Hope this helps, Richard R On Mar 31, 2010, at 10:02 AM, Jason Fowler wrote: Hi all, I am testing DSpace 1.6 before we migrate to it. I believe I have the dspace.cfg set up correctly, and I have added dc.embargo.terms and dc.embargo.liftdate to my metadata registry. However, nothing shows up in the submission workflow in any of my xmlui themes, or in jspui. Are there additional changes that I need to make in order to enable this within the workflow? Can someone explain what those are? Thanks, Jason Fowler, CA, MSLS Archives and Special Collections Librarian The Southern Baptist Theological Seminary Vice President, ALABI jfow...@sbts.edu -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Embargoes in 1.6
Richard, That's helpful. So just to verify, it is necessary to add those items to the input-forms.xml in order to get them to show up in the submission process? Embargoes don't just work (ie. show up in the submission process) out of the box? I am fine with making the changes, but I just want to make sure they are actually necessary. Thanks, Jason -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Embargoes in 1.6
Hello Jason, the embargo only works during the submission process not if you edit add the metadata to an already archived item. It will not make the item invisible but restrict the access to the bitstreams belonging to an item, set a lift date and change the date available. When the embargo is lifted the resource policies are inherited from the owning collections default settings. Apart from the changes in dspace.cfg and metadata registry you got to add the administrative.embargo.terms as a field to the input-forms.xml, for testing purposes best as a date field, e.g. field dc-schemafoo/dc-schema dc-elementembargo/dc-element dc-qualifierterms/dc-qualifier repeatablefalse/repeatable labelDate of embargo duration/label input-typedate/input-type hintSome explanatory text/hint required/required /field You can create your own setter and use terms like 6 months, 1 year etc on which base the lift date will be computed. Hope that helps Claudia Jürgen Am 31.03.2010 16:02, schrieb Jason Fowler: Hi all, I am testing DSpace 1.6 before we migrate to it. I believe I have the dspace.cfg set up correctly, and I have added dc.embargo.terms and dc.embargo.liftdate to my metadata registry. However, nothing shows up in the submission workflow in any of my xmlui themes, or in jspui. Are there additional changes that I need to make in order to enable this within the workflow? Can someone explain what those are? Thanks, Jason Fowler, CA, MSLS Archives and Special Collections Librarian The Southern Baptist Theological Seminary Vice President, ALABI jfow...@sbts.edu -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech attachment: Claudia_Juergen.vcf-- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Embargoes in 1.6
Jason: Yes, that's right - input-forms must be updated. But I regard it on balance an advantage that the embargo system 'inherits' all the configurability of standard DSpace metadata - not just in submission, but indexing, display and more (so you could, e.g. do fielded search on embargo dates, or suppress display in the 'simple' item page, etc). However, this flexibility does add additional configuration steps initially, as you observe. Thanks, Richard On Mar 31, 2010, at 10:24 AM, Jason Fowler wrote: Richard, That's helpful. So just to verify, it is necessary to add those items to the input-forms.xml in order to get them to show up in the submission process? Embargoes don't just work (ie. show up in the submission process) out of the box? I am fine with making the changes, but I just want to make sure they are actually necessary. Thanks, Jason -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Embargoes in 1.6
Hi All With respect to older items already submitted, can one impose an embargo on them without a migration and re-submission ? Cheers hg. On 31 March 2010 16:21, Richard Rodgers rrodg...@mit.edu wrote: Hi Jason: One thought: have you added those fields to your input-forms.xml? In other respects, the embargo fields behave just like any other metadata, and can be added to the default set - or any collection-specifc set - of metadata fields used in web submission. The tech doc has instructions on managing input-forms. Hope this helps, Richard R On Mar 31, 2010, at 10:02 AM, Jason Fowler wrote: Hi all, I am testing DSpace 1.6 before we migrate to it. I believe I have the dspace.cfg set up correctly, and I have added dc.embargo.terms and dc.embargo.liftdate to my metadata registry. However, nothing shows up in the submission workflow in any of my xmlui themes, or in jspui. Are there additional changes that I need to make in order to enable this within the workflow? Can someone explain what those are? Thanks, Jason Fowler, CA, MSLS Archives and Special Collections Librarian The Southern Baptist Theological Seminary Vice President, ALABI jfow...@sbts.edu -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Systems Administrator Library and Information Services Stellenbosch University http://www.sun.ac.za http://library.sun.ac.za http://scholar.sun.ac.za http://ubuntu.sun.ac.za -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Embargoes in 1.6
That makes sense. The only thing I don't understand is how exactly the liftdate is computed. Is that something that happens automatically, or do I need to configure that? Jason Fowler, CA, MSLS From: Claudia Juergen [claudia.juer...@ub.tu-dortmund.de] Sent: Wednesday, March 31, 2010 12:14 PM To: Jason Fowler Cc: claudia.juer...@ub.tu-dortmund.de Subject: RE: [Dspace-tech] Embargoes in 1.6 Hello Jason, only the embargo terms afaik. The liftdate is computed based upon the terms. Claudia Thanks, Claudia! Just one more question. Do I need to add both dc.embargo.terms AND dc.embargo.liftdate to the input-forms.xml? Thanks in advance, Jason Fowler, CA, MSLS -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Embargoes in 1.6
Hi Hilton: Not really - the assumption of the embargo system is that once content has been made generally available, it no longer makes sense to embargo it (since embargo traditionally means withholding exposure until some future time, then exposing it). So it really isn't the same as access restriction, which can be accomplished with standard DSpace administrative tools [and admin changes can me made anytime]. Does that make sense? Thanks, Richard On Mar 31, 2010, at 1:20 PM, Hilton Gibson wrote: Hi All With respect to older items already submitted, can one impose an embargo on them without a migration and re-submission ? Cheers hg. On 31 March 2010 16:21, Richard Rodgers rrodg...@mit.edumailto:rrodg...@mit.edu wrote: Hi Jason: One thought: have you added those fields to your input-forms.xml? In other respects, the embargo fields behave just like any other metadata, and can be added to the default set - or any collection-specifc set - of metadata fields used in web submission. The tech doc has instructions on managing input-forms. Hope this helps, Richard R On Mar 31, 2010, at 10:02 AM, Jason Fowler wrote: Hi all, I am testing DSpace 1.6 before we migrate to it. I believe I have the dspace.cfg set up correctly, and I have added dc.embargo.terms and dc.embargo.liftdate to my metadata registry. However, nothing shows up in the submission workflow in any of my xmlui themes, or in jspui. Are there additional changes that I need to make in order to enable this within the workflow? Can someone explain what those are? Thanks, Jason Fowler, CA, MSLS Archives and Special Collections Librarian The Southern Baptist Theological Seminary Vice President, ALABI jfow...@sbts.edumailto:jfow...@sbts.edu -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.netmailto:DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.netmailto:DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Systems Administrator Library and Information Services Stellenbosch University http://www.sun.ac.zahttp://www.sun.ac.za/ http://library.sun.ac.zahttp://library.sun.ac.za/ http://scholar.sun.ac.zahttp://scholar.sun.ac.za/ http://ubuntu.sun.ac.zahttp://ubuntu.sun.ac.za/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Embargoes in 1.6
On 31 March 2010 20:35, Richard Rodgers rrodg...@mit.edu wrote: Hi Hilton: Not really - the assumption of the embargo system is that once content has been made generally available, it no longer makes sense to embargo it (since embargo traditionally means withholding exposure until some future time, then exposing it). So it really isn't the same as access restriction, which can be accomplished with standard DSpace administrative tools [and admin changes can me made anytime]. Does that make sense? Yes. But and there is always a but. What we did before 1.6.0 was to remove the binary object. Now we want to restore them but with an embargo. How do we do that ? See: http://ir.sun.ac.za/wiki/index.php/Asset_Embargo. Check procedure - option b. Will this work ? Cheers hg. Thanks, Richard On Mar 31, 2010, at 1:20 PM, Hilton Gibson wrote: Hi All With respect to older items already submitted, can one impose an embargo on them without a migration and re-submission ? Cheers hg. On 31 March 2010 16:21, Richard Rodgers rrodg...@mit.edu wrote: Hi Jason: One thought: have you added those fields to your input-forms.xml? In other respects, the embargo fields behave just like any other metadata, and can be added to the default set - or any collection-specifc set - of metadata fields used in web submission. The tech doc has instructions on managing input-forms. Hope this helps, Richard R On Mar 31, 2010, at 10:02 AM, Jason Fowler wrote: Hi all, I am testing DSpace 1.6 before we migrate to it. I believe I have the dspace.cfg set up correctly, and I have added dc.embargo.terms and dc.embargo.liftdate to my metadata registry. However, nothing shows up in the submission workflow in any of my xmlui themes, or in jspui. Are there additional changes that I need to make in order to enable this within the workflow? Can someone explain what those are? Thanks, Jason Fowler, CA, MSLS Archives and Special Collections Librarian The Southern Baptist Theological Seminary Vice President, ALABI jfow...@sbts.edu -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Systems Administrator Library and Information Services Stellenbosch University http://www.sun.ac.za http://library.sun.ac.za http://scholar.sun.ac.za http://ubuntu.sun.ac.za -- Systems Administrator Library and Information Services Stellenbosch University http://www.sun.ac.za http://library.sun.ac.za http://scholar.sun.ac.za http://ubuntu.sun.ac.za -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Embargoes in 1.6
Hi Jason: I can see that this might be confusing, so let me try to explain a little more clearly. At the most basic level, the field containing the 'terms' is where a submitter specifies how the embargo should work for that item. At the time of installation into the archive (i.e. when it exits workflow) those terms are 'interpreted' into a specific date in the future, which is then stored in the 'liftdate' field. The lifter then only checks this latter date, and ignores the original 'terms'. What can the terms be? Conceivably anything, (e.g. 60 days, my standard policy, Elsevier terms, etc), but of course the software cannot interpret arbitrary words. That's why the embargo system allows you to write your own code that interprets whatever terms you want to use, and will run that code at the appropriate time. However, 'out of the box', DSpace supplies code for the simplest case: that in which the terms are actual dates themselves. In this case, all it does is copy the date you put in 'terms' into 'liftdate'. Over time, as we discover other common 'terms', we can add to the DSpace 'library' of term-interpreting code, and distribute them with each new release. Finally, (to really confuse things), you can actually configure the 'terms' dc field to be the same as the 'liftdate' field! That is, make 'dc.embargo' or whatever you want serve as both terms and lift. In this case, it doesn't even copy a field, it just uses the date 'in place'. This is really a sensible configuration, if you don't want to keep a permanent record of what the terms were. Does that illuminate things a bit? Richard On Mar 31, 2010, at 1:59 PM, Jason Fowler wrote: That makes sense. The only thing I don't understand is how exactly the liftdate is computed. Is that something that happens automatically, or do I need to configure that? Jason Fowler, CA, MSLS From: Claudia Juergen [claudia.juer...@ub.tu-dortmund.de] Sent: Wednesday, March 31, 2010 12:14 PM To: Jason Fowler Cc: claudia.juer...@ub.tu-dortmund.de Subject: RE: [Dspace-tech] Embargoes in 1.6 Hello Jason, only the embargo terms afaik. The liftdate is computed based upon the terms. Claudia Thanks, Claudia! Just one more question. Do I need to add both dc.embargo.terms AND dc.embargo.liftdate to the input-forms.xml? Thanks in advance, Jason Fowler, CA, MSLS -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] Embargoes in 1.6
Hi Hilton: I'm not sure I precisely follow option b (especially step 9 - not sure what 'read access permission problems' are), but something along these lines ought to work. Specifically, if by some means you remove read policies on the bitstreams, and make sure there is a valid date in the field configured for the liftdate, then regularly running the lifter will lift the embargo on those items at the time you set. You don't really even need any values in the 'terms' field at all, since the lifter doesn't check or use it. The only rub I can see is that each item would have to be manually assigned a lift date and have it's read policies removed - the embargo stuff doesn't have batch tools for this. Does this address your question? Richard On Mar 31, 2010, at 2:59 PM, Hilton Gibson wrote: On 31 March 2010 20:35, Richard Rodgers rrodg...@mit.edumailto:rrodg...@mit.edu wrote: Hi Hilton: Not really - the assumption of the embargo system is that once content has been made generally available, it no longer makes sense to embargo it (since embargo traditionally means withholding exposure until some future time, then exposing it). So it really isn't the same as access restriction, which can be accomplished with standard DSpace administrative tools [and admin changes can me made anytime]. Does that make sense? Yes. But and there is always a but. What we did before 1.6.0 was to remove the binary object. Now we want to restore them but with an embargo. How do we do that ? See: http://ir.sun.ac.za/wiki/index.php/Asset_Embargo. Check procedure - option b. Will this work ? Cheers hg. Thanks, Richard On Mar 31, 2010, at 1:20 PM, Hilton Gibson wrote: Hi All With respect to older items already submitted, can one impose an embargo on them without a migration and re-submission ? Cheers hg. On 31 March 2010 16:21, Richard Rodgers rrodg...@mit.edumailto:rrodg...@mit.edu wrote: Hi Jason: One thought: have you added those fields to your input-forms.xml? In other respects, the embargo fields behave just like any other metadata, and can be added to the default set - or any collection-specifc set - of metadata fields used in web submission. The tech doc has instructions on managing input-forms. Hope this helps, Richard R On Mar 31, 2010, at 10:02 AM, Jason Fowler wrote: Hi all, I am testing DSpace 1.6 before we migrate to it. I believe I have the dspace.cfg set up correctly, and I have added dc.embargo.terms and dc.embargo.liftdate to my metadata registry. However, nothing shows up in the submission workflow in any of my xmlui themes, or in jspui. Are there additional changes that I need to make in order to enable this within the workflow? Can someone explain what those are? Thanks, Jason Fowler, CA, MSLS Archives and Special Collections Librarian The Southern Baptist Theological Seminary Vice President, ALABI jfow...@sbts.edumailto:jfow...@sbts.edu -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.netmailto:DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.netmailto:DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Systems Administrator Library and Information Services Stellenbosch University http://www.sun.ac.zahttp://www.sun.ac.za/ http://library.sun.ac.zahttp://library.sun.ac.za/ http://scholar.sun.ac.zahttp://scholar.sun.ac.za/ http://ubuntu.sun.ac.zahttp://ubuntu.sun.ac.za/ -- Systems Administrator Library and Information Services Stellenbosch University http://www.sun.ac.zahttp://www.sun.ac.za/ http://library.sun.ac.zahttp://library.sun.ac.za/ http://scholar.sun.ac.zahttp://scholar.sun.ac.za/ http://ubuntu.sun.ac.zahttp://ubuntu.sun.ac.za/ -- Download Intel#174; Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta.
