Let me know
How many items can be ingested through .CSV import method?
Opening CSV with Excel is light critical. because it may not open properly
every time.
Thank you
On Mon, Aug 5, 2013 at 10:48 PM, <
[email protected]> wrote:
> Send Dspace-general mailing list submissions to
> [email protected]
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/dspace-general
> or, via email, send a message with subject or body 'help' to
> [email protected]
>
> You can reach the person managing the list at
> [email protected]
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dspace-general digest..."
>
> Today's Topics:
>
> 1. Re: How to Get Started (helix84)
> 2. Re: How to Get Started (helix84)
> 3. Re: How to Get Started (Thomas Ronayne)
> 4. Re: How to Get Started (helix84)
> 5. Re: How to Get Started (Hilton Gibson)
>
>
> ---------- Forwarded message ----------
> From: helix84 <[email protected]>
> To: Thomas Ronayne <[email protected]>
> Cc: DSpace-General <[email protected]>
> Date: Mon, 5 Aug 2013 14:19:21 +0200
> Subject: Re: [Dspace-general] How to Get Started
> Hi Thomas,
>
> the first thing you'll want to do is to define which metadata fields
> you'll be using and which ones of those are missing from the default
> metadata registry in DSpace. You should add all those you'll be using.
> Don't worry too much to get it right the first time - you can change
> it at any later time.
>
> Second thing is actually adding an item. First try it with one book -
> use the submission process. Log in as admin and go to a collection
> (communities cannot contain items, they contain only subcommunities
> and collections). You should see a link to start submission there. The
> submission process is several pages long, but only a few fields are
> required.
>
> Once you have tried out adding a single item, you'll see that it's
> unpractical to use for thousands of them. So you'll choose one of tha
> available batch import methods [1]. I'd recommend you to use Batch
> Metadata Editing (typing all metadata into a single CSV file), because
> it's easiest. The drawback is that it works only with metadata, and
> you'll have to upload bitstreams separately. To prepare a "template"
> CSV file, do a CSV export first (after adding metadata fields as I
> wrote above). You'll see that column headers are metadata field names.
> To add a new item, put "+" into the "id" column. The "collection"
> column is mandatory and I strongly recommend you to also fill in at
> least the dc.title field (otherwise some weird situations can occur).
>
> [1]
> https://wiki.duraspace.org/display/DSPACE/EndUserFaq#EndUserFaq-CanIimportcontentintoDSpaceinbatchmode
> ?
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
>
>
> ---------- Forwarded message ----------
> From: helix84 <[email protected]>
> To: Thomas Ronayne <[email protected]>
> Cc: DSpace-General <[email protected]>
> Date: Mon, 5 Aug 2013 14:20:39 +0200
> Subject: Re: [Dspace-general] How to Get Started
> On Mon, Aug 5, 2013 at 2:19 PM, helix84 <[email protected]> wrote:
> > define which metadata fields
> > you'll be using and which ones of those are missing from the default
> > metadata registry in DSpace. You should add all those you'll be using.
>
> To do that, log in as admin and go to Registries - Metadata in the admin
> menu.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
>
>
> ---------- Forwarded message ----------
> From: Thomas Ronayne <[email protected]>
> To: [email protected]
> Cc: DSpace-General <[email protected]>
> Date: Mon, 05 Aug 2013 12:03:22 -0400
> Subject: Re: [Dspace-general] How to Get Started
> Hi, Helix84,
>
> OK, thanks for that -- starting to make more sense.
>
> Here's the thing -- I've been bouncing around Dublin Core and danged if I
> can find some of the really basic stuff I need to record (maybe I just
> haven't followed the right link yet, eh?).
>
> The basic stuff I do need to record:
>
> - Title
> - Author
> - Type (book, monograph, notes, document)
> - Size
> - Subject
> - Illustrator
> - Publisher (name, location)
> - Date
> - Printer (name, location)
> - Date
> - Binding
> - Binder (name, location)
> - Date
> - Acquired (Dealer, location)
> - Date
> - Cost
> - Language (English, Old- and New French, German, Latin, Greek,
> Portuguese, Spanish, Italian; ISO codes, of course)
> - Evaluator
> - Date Evaluated
> - Condition
> - Notes
>
> The contributor is one person, a constant, which may be ignored or may be
> batch updated -- everything is from one estate.
>
> I can figure out most of it, but danged if I've been able to find where to
> put dealer, cost, evaluator and maybe illustrator (many volumes are
> illustrated with original art in various formats; e.g., copper etchings
> from, oh, 1620). We have first editions illustrated by George Cruikshank,
> kind of an important guy in the 19th century. It would be convenient to
> define a field, and I have no clue on this one, for a chain of ownership;
> e.g., one recent volume I evaluated contained the original owner's
> hand-written signature and address: "George R, Hampton Court" (there would
> only be one George R(egent) resident at Hampton Court -- see what I mean?).
> There are a number of presentation copies (the pages aren't trimmed, not
> meant to have been read).
>
> Most of the list I've been able to find or figure out, but there are those
> that I haven't and I know those will be mandatory so I need to figure them
> out, too. I've been looking at Using Dublin
> Core<http://www.dublincore.org/documents/usageguide/>(out-of-date, but it's
> got examples in it) and getting a better feel for
> how to use it; I've also been reading through Dublin Core Metadata
> Element Set v. 1.1 <http://www.dublincore.org/documents/dces/> (no
> examples, but more in-depth). But, cost? Nope, nowhere to be found (and I
> can't imagine anybody not wanting to record where I got it and how much I
> paid for it).
>
> You know, if I'd just done a LAMP data base I'd have been done weeks ago
> -- but, big but, it wouldn't adhere to any particular standard and would be
> just as useless and the FoxBase thing we've already got (with few, really,
> really few, entries in it). So I'm pretty sure DSpace is worth the effort
> and I am grateful for the help and advice, thanks.
>
> Thomas
>
> A riddle, wrapped in a mystery, inside an enigma but that's my story and I'm
> stickin' to it.
>
> On 08/05/2013 08:20 AM, helix84 wrote:
>
> On Mon, Aug 5, 2013 at 2:19 PM, helix84 <[email protected]>
> <[email protected]> wrote:
>
> define which metadata fields
> you'll be using and which ones of those are missing from the default
> metadata registry in DSpace. You should add all those you'll be using.
>
> To do that, log in as admin and go to Registries - Metadata in the admin
> menu.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List
> Etiquettehttps://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
>
>
> ---------- Forwarded message ----------
> From: helix84 <[email protected]>
> To: Thomas Ronayne <[email protected]>
> Cc: DSpace-General <[email protected]>
> Date: Mon, 5 Aug 2013 18:16:08 +0200
> Subject: Re: [Dspace-general] How to Get Started
> On Mon, Aug 5, 2013 at 6:03 PM, Thomas Ronayne <[email protected]>
> wrote:
> > Here's the thing -- I've been bouncing around Dublin Core and danged if I
> > can find some of the really basic stuff I need to record (maybe I just
> > haven't followed the right link yet, eh?).
>
> It's OK, it takes time getting used to. I'd say everyone curses their
> first schema and learns wth their second one.
>
> > The contributor is one person, a constant, which may be ignored or may be
> > batch updated -- everything is from one estate.
>
> Don't put it into dc.contributor. DSpace uses dc.contributor.author
> for the actual author and you wouldn't want to mix these up, which
> could happen e.g. when crosswalking QDC to DC. Create your own field
> for your "contributor", which brings me to the most important advice -
> don't touch the "dc" namespace, create your own namespace called
> "local" and create any new fields solely in there. What seems to fit
> into dc, put to dc; put the rest into your own "local" namespace.
>
> > It would be convenient to
> > define a field, and I have no clue on this one, for a chain of ownership;
> > e.g., one recent volume I evaluated contained the original owner's
> > hand-written signature and address: "George R, Hampton Court" (there
> would
> > only be one George R(egent) resident at Hampton Court -- see what I
> mean?).
>
> There is a thing called "authorities" for this (for creating an ID for
> a single person/string), but currently they're easily usable only on
> one field. You'll probably want that field to be the author and you'll
> probably want to postpone implementing authorities for later; it's an
> advanced topic.
>
> > Most of the list I've been able to find or figure out, but there are
> those
> > that I haven't and I know those will be mandatory so I need to figure
> them
> > out, too.
>
> Yep, see above - your custom "local" schema. Define it anyway you see fit.
>
>
> Regards,
> ~~helix84
>
> Compulsory reading: DSpace Mailing List Etiquette
> https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>
>
>
>
> ---------- Forwarded message ----------
> From: Hilton Gibson <[email protected]>
> To: Thomas Ronayne <[email protected]>
> Cc: DSpace-General <[email protected]>
> Date: Mon, 5 Aug 2013 19:17:51 +0200
> Subject: Re: [Dspace-general] How to Get Started
> Perhaps this will help:
> http://wiki.lib.sun.ac.za/index.php/SUNScholar/Metadata or ask the NSA;-)
>
>
> On 5 August 2013 18:03, Thomas Ronayne <[email protected]> wrote:
>
>> Hi, Helix84,
>>
>> OK, thanks for that -- starting to make more sense.
>>
>> Here's the thing -- I've been bouncing around Dublin Core and danged if I
>> can find some of the really basic stuff I need to record (maybe I just
>> haven't followed the right link yet, eh?).
>>
>> The basic stuff I do need to record:
>>
>> - Title
>> - Author
>> - Type (book, monograph, notes, document)
>> - Size
>> - Subject
>> - Illustrator
>> - Publisher (name, location)
>> - Date
>> - Printer (name, location)
>> - Date
>> - Binding
>> - Binder (name, location)
>> - Date
>> - Acquired (Dealer, location)
>> - Date
>> - Cost
>> - Language (English, Old- and New French, German, Latin, Greek,
>> Portuguese, Spanish, Italian; ISO codes, of course)
>> - Evaluator
>> - Date Evaluated
>> - Condition
>> - Notes
>>
>> The contributor is one person, a constant, which may be ignored or may be
>> batch updated -- everything is from one estate.
>>
>> I can figure out most of it, but danged if I've been able to find where
>> to put dealer, cost, evaluator and maybe illustrator (many volumes are
>> illustrated with original art in various formats; e.g., copper etchings
>> from, oh, 1620). We have first editions illustrated by George Cruikshank,
>> kind of an important guy in the 19th century. It would be convenient to
>> define a field, and I have no clue on this one, for a chain of ownership;
>> e.g., one recent volume I evaluated contained the original owner's
>> hand-written signature and address: "George R, Hampton Court" (there would
>> only be one George R(egent) resident at Hampton Court -- see what I mean?).
>> There are a number of presentation copies (the pages aren't trimmed, not
>> meant to have been read).
>>
>> Most of the list I've been able to find or figure out, but there are
>> those that I haven't and I know those will be mandatory so I need to figure
>> them out, too. I've been looking at Using Dublin
>> Core<http://www.dublincore.org/documents/usageguide/>(out-of-date, but it's
>> got examples in it) and getting a better feel for
>> how to use it; I've also been reading through Dublin Core Metadata
>> Element Set v. 1.1 <http://www.dublincore.org/documents/dces/> (no
>> examples, but more in-depth). But, cost? Nope, nowhere to be found (and I
>> can't imagine anybody not wanting to record where I got it and how much I
>> paid for it).
>>
>> You know, if I'd just done a LAMP data base I'd have been done weeks ago
>> -- but, big but, it wouldn't adhere to any particular standard and would be
>> just as useless and the FoxBase thing we've already got (with few, really,
>> really few, entries in it). So I'm pretty sure DSpace is worth the effort
>> and I am grateful for the help and advice, thanks.
>>
>> Thomas
>>
>> A riddle, wrapped in a mystery, inside an enigma but that's my story and I'm
>> stickin' to it.
>>
>> On 08/05/2013 08:20 AM, helix84 wrote:
>>
>> On Mon, Aug 5, 2013 at 2:19 PM, helix84 <[email protected]>
>> <[email protected]> wrote:
>>
>> define which metadata fields
>> you'll be using and which ones of those are missing from the default
>> metadata registry in DSpace. You should add all those you'll be using.
>>
>> To do that, log in as admin and go to Registries - Metadata in the admin
>> menu.
>>
>>
>> Regards,
>> ~~helix84
>>
>> Compulsory reading: DSpace Mailing List
>> Etiquettehttps://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Get your SQL database under version control now!
>> Version control is standard for application code, but databases havent
>> caught up. So what steps can you take to put your SQL databases under
>> version control? Why should you start doing it? Read more to find out.
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
>> _______________________________________________
>> Dspace-general mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/dspace-general
>>
>>
>
>
> --
> *Hilton Gibson*
> Ubuntu Linux Systems Administrator
> JS Gericke Library
> Room 1025D
> Stellenbosch University
> Private Bag X5036
> Stellenbosch
> 7599
> South Africa
>
> Tel: +27 21 808 4100 | Cell: +27 84 646 4758
> http://library.sun.ac.za
> http://za.linkedin.com/in/hiltongibson
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Dspace-general mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dspace-general
>
>
--
Regards
Mr. Shivraj Thorat
Librarian
BVDU, Institute of Management & Entrepreneurship Development
Paud Rd, Kothrud,
Pune-38
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Dspace-general mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-general
