Re: [Dspace-tech] importing classified collection
Hi P. Hadadan, Unfortunately, DSpace doesn't support importing entire folder structures into Collections. A list of all valid ways to import content into DSpace is in the Documentation at: https://wiki.duraspace.org/display/DSDOC4x/Ingesting+Content+and+Metadata Likely, in this scenario, since you already have folders, your best option would be to try to translate/transform these into DSpace Simple Archive Format folders. See: https://wiki.duraspace.org/display/DSDOC4x/Importing+and+Exporting+Items+via+Simple+Archive+Format However, that only works for *items*. So, for any Communities/Collections, you'd have to create them manually or import the hierarchy by creating a Community/Collection XML file. See: https://wiki.duraspace.org/display/DSDOC4x/Importing+Community+and+Collection+Hierarchy I know it's probably not the news you were looking for, but these seem like your best options. - Tim On 9/29/2014 7:07 AM, P.Hadadan (NW) wrote: Dears, I want to import a collection into dspace. The collection includes segmentation is based on directory .For example, the directory #1 contains two folders, folder #1 and folder #2. Folder #1 contains 3 items and folder #2 includes an Item and a folder containing 5 items. *[items format : XML(metadata), pdf, word, image, …] How can I *_automatically_* classified and import data into dspace collection based on my collection ? Please give me your experience about this. Sincerely, *P.Hadadan | *Senior Software Developer NotionWave | Toronto, Canada P.Hadadan [at] notionwave [dot] com -- Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] [Dspace-devel] DSpace 5: Dates and Features
Reminder to all: DSpace 5 New Feature Pull Request Deadline Day is TODAY!! So, if you are planning to contribute something for DSpace 5, you will need to stay up all night and code, code, code, and then submit your pull request. We would prefer that features be mostly complete. Over the review process, expect that there might be a few bug-fixes or final improvements to make based on testing and suggestions by others. Also, to Hayden. There is a CRUD REST PR made by Czech Technical University in Prague CZ. https://github.com/DSpace/DSpace/pull/666 I'm currently evaluating that. It appears that it has some auth scheme where your consumer makes a request to /login, passing username/password, and receives a token in response. Further communication requires that token. It appears to require SSL. Peter Dietz Longsight www.longsight.com pe...@longsight.com p: 740-599-5005 x809 On Thu, Sep 11, 2014 at 10:44 AM, Peter Dietz pe...@longsight.com wrote: Hi Hayden, Thanks for your interest in DSpace 4+ REST (Jersey). The readme has info on the endpoints: https://github.com/DSpace/DSpace/tree/master/dspace-rest Is it compatible, to go from a previous REST API, to the current Jersey API? It depends. Play! Framework client (demo): http://dspace-rest-client-play.herokuapp.com/ Ruby on Rails client (demo): http://dspace-rails.herokuapp.com/ It might not have all the information your looking for, especially if you are expecting to receive restricted content, or to do CRUD actions. Recent development on the REST/Jersey api have been to work on search, and viewing statistics (thanks Anja). I expect to have that cleaned up, and merged in, before DSpace 5 release. Kim Shepherd and I have been discussing authentication. I'm in favor of using OAUTH1. But essentially, I don't want to add any CRUD endpoints, until we have authentication solidly figured out. i.e. It might work for one institution to hack something like ?epersonID=1 to authenticate within your firewall, but another institution might miss on some security concerns. So, I'm thinking its best to have an authentication stack that works great when complemented with SSL, but, can still securely transfer auth tokens without ssl. At Open Repository 2014, I heard that there were some groups that had added additional CRUD endpoints, to allow them to integrate their LMS/gradebook with DSpace REST (jersey), but skipped auth, since it was within their firewall. It would be interesting to hear from that group, and or see some code. So yes, ideally I would love to have proper auth, and full CRUD endpoints in DSpace REST in time for DSpace 5. I personally have a lot of my plate, that I don't see myself accomplishing that alone. Peter Dietz Longsight www.longsight.com pe...@longsight.com p: 740-599-5005 x809 On Thu, Sep 11, 2014 at 9:54 AM, Hayden Young haydenyo...@wijiti.com wrote: What is the current situation on the Jersey REST API bundled with DSpace 5 in regards to the additional endpoints documented at https://wiki.duraspace.org/display/DSPACE/REST+API. We are attempting to support the Jersey REST API for existing production DSpace instances by using the documented endpoints, in particular bitstream retrieval and writing back to the DSpace archive. Additionally, what is the current status on alternative user authentication mechanisms in Jersey REST? The documentation discusses username/password being passed as part of the url although I believe there was discussion around other authentication functions being implemented. Cheers Hayden email. hay...@knowledgearc.com web. http://knowledgearc.com, http://knowledgearc.org On 10/09/14 23:10, Peter Dietz wrote: Greetings from the DSpace 5.0 Release Team! We have another exciting release of DSpace in the works that has been growing steadily over the past few months. Many contributors have been busy adding new features and improvements to DSpace. This speaks volumes to the maturity, stability, and future of DSpace, that as the software project approaches its 12th year, we're still going strong. Read on for ways to help contribute, and find out the new features in DSpace 5. The full release schedule is here: https://wiki.duraspace.org/display/DSPACE/DSpace+Release+5.0+Status October 6: Deadline for Feature Pull Requests In plain English, October 6 is the last day you may submit new features for acceptance into DSpace 5.0. If you are working on a new feature for DSpace, we urge you to prepare a Pull Request now. Getting your work visible early as a Pull Request allows others to review, and help steer your contribution to inclusion in the next release. Here’s how: https://wiki.duraspace.org/display/DSPACE/Code+Contribution+Guidelines Other Important Dates: October 31 5.beta-1 - Release Candidate 1 November 03-14 Testathon (mark your calendar) November 20 5.beta-2 - Release Candidate 2
[Dspace-tech] requiring login to view files
Hello, I want to require authentication to view files within communities and collections. I'm using release 3.2. Does someone know the changes I would make to the configuration file in order to do this? Thank you, Mary Weppler -- Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
Re: [Dspace-tech] requiring login to view files
Hi Mary, As I understand your problem, there's no config to change to make this happen. Currently, all of your bitstreams probably are open access, anybody on the internet can access them, no login required. One low-tech solution to this problem could be to create a new eperson Group, call it something like Users. Then you'll have to edit all of your existing bitstreams, remove Anonymous READ, and add group Users READ. It would be wise to alter your collections to be Users READ by default all new submissions then. Then, for people who register on your site, they create an EPerson. You would then have to add those people to the Users account manually, each time they register on your site. If you've got something like LDAP or Shibboleth for your institution, the adding users to groups is less manual. You would just map users to groups based on shib credentials, and then all shibboleth users are automatically mapped to that group you specify. Peter Dietz Longsight www.longsight.com pe...@longsight.com p: 740-599-5005 x809 On Mon, Oct 6, 2014 at 7:39 PM, Mary Weppler-Selear mweppler-sel...@ucmerced.edu wrote: Hello, I want to require authentication to view files within communities and collections. I'm using release 3.2. Does someone know the changes I would make to the configuration file in order to do this? Thank you, Mary Weppler -- Slashdot TV. Videos for Nerds. Stuff that Matters. http://pubads.g.doubleclick.net/gampad/clk?id=160591471iu=/4140/ostg.clktrk ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette -- Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS Reports Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer http://pubads.g.doubleclick.net/gampad/clk?id=154622311iu=/4140/ostg.clktrk___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
