[Dspace-general] answer for metadata harvest

Fri Jun 25 01:30:14 EDT 2004

       respected sir, i am srinivas from university of mysore ,harvested metadata will helps to retrive the document world wide,if we use the metadata creator&source it will not only helps to create a metadata for the guven docment.the open archive initiative-protocal metadataharvest[oai-pmh] will reduce the barrier of interoprasility.
       please give me the answer sir .and iam doing project on collection of R.K.NARAYAN :A NOVALIST using dspace so i have to instal dspace iam not getting ds software can u send me ds cd new version to my address  
              SRINIVAS.P.S
              #10,1st 'A' MAINROAD,POSTALCOLONY,METAGALLI,MYSORE-      
               570016,KARNATAKA,INDIA, 

dspace-general-request at mit.edu wrote:
Send Dspace-general mailing list submissions to
dspace-general at mit.edu

To subscribe or unsubscribe via the World Wide Web, visit
http://mailman.mit.edu/mailman/listinfo/dspace-general
or, via email, send a message with subject or body 'help' to
dspace-general-request at mit.edu

You can reach the person managing the list at
dspace-general-owner at mit.edu

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Dspace-general digest..."

Today's Topics:

1. metadata: source and creator (dp007)
2. entering custom keywords with drop-down list?
(=?ISO-8859-1?Q?J=F6rn_Nettingsmeier?=)
3. Re: metadata: source and creator (Margret Branschofsky)

----------------------------------------------------------------------

Date: Mon, 21 Jun 2004 02:48:37 +0550
From: "dp007" 
To: dspace-general at mit.edu
Subject: [Dspace-general] metadata: source and creator
Message-ID: <1087762717.3020836925 at as03.coolgoose.com>
Precedence: list
Message: 1

hi all,

dspace recommends not to use the metadata creator and source. it 
says "only for harvested metadata". can anyone explain this?

thanks in advance,
regards,
dp
------------------------------

Date: Mon, 21 Jun 2004 12:11:41 +0200
From: =?ISO-8859-1?Q?J=F6rn_Nettingsmeier?= 

To: dspace-general at mit.edu
Subject: [Dspace-general] entering custom keywords with drop-down list?
Message-ID: <40D6B45D.2070302 at uni-duisburg.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: list
Message: 2

hi fellow dspacers!

i'm doing a dspace setup for a little research project. they want to use 
one collection for their published results and one as an internal 
document stash for research material - clippings and some dummy entries 
(metadata only and no documents).

they have made up their own keyword thesaurus to quickly categorize 
those clippings. i'm using dc.subject.other for the keywords, and i 
would love to have some sort of drop-down box in the submission pages 
where users can select one or more of those pre-defined keywords, 
instead of (mis-)typing them in by hand.

i'm aware that html s do not scale very well for large keyword bidies, but they would be soooo nice to have in my particular case.i've seen tab completion somewhere, which even better nice, scales well, but is probably very hairy to implement and requires client-side caching of the keywords......any comments?best,jörn-- Jörn Nettingsmeier, EDV-AdministratorInstitut für PolitikwissenschaftUniversität Duisburg-Essen, Standort DuisburgMail: pol-admin at uni-duisburg.de, Telefon: 0203/379-2736------------------------------Date: Mon, 21 Jun 2004 11:47:36 -0400From: Margret Branschofsky To: "dp007" , dspace-general at MIT.EDUSubject: Re: [Dspace-general] metadata: source and creatorMessage-ID: <5.2.1.1.2.20040621112701.0cbe6450 at po10.mit.edu>In-Reply-To: <1087762717.3020836925 at as03.coolgoose.com>Content-Type: multipart/alternative; boundary="=====================_267419849==.ALT"MIME-Version: 1.0Precedence: listMessage: 3--=====================_267419849==.ALTContent-Type: text/plain;
 charset="us-ascii"; format=flowedDSpace uses the Contributor element instead of the Creator element because this relieves the user of the burden of deciding who, of all the people involved in the production of an item, is "primarily responsible" in the creation of the item. We added roles to contributor, thinking that was more specific than the vague "creator" field. So we have Contributor. author, Contributor.editor, Contributor.illustrator...etc. And if anyone wants to leave it vague, they can use the unqualified Contributor field.Our guide in this decision was the Libraries Application Profile (LAP) of the Dublin Core, which was in an early draft stage at the time of DSpace launching. This draft conflated the Contributor and Creator elements into one. When the DC Libraries Group published the present draft of the LAP (officially called DC-Lib), the contributor and creator elements reappeared as separate elements. However, there is a comment under both of these elements t!
 hat
 states "Creator and Contributor may be conflated if desired by the application".We left Creator in our schema only because we anticipated that we might in the future harvest metadata that contains values in the Creator element, and we wanted to be able to accept that information.As time goes by we see that this decision is proving to be somewhat inconvenient for metadata harvesters.As for Source, at the time of DSpace launching the LAP (and also the DCMI) were counseling people not to use Source because it had been mis-used by some applications, in their opinion. Since then I have seen its use being recommended again, so it might be time for us to change that line in our guidelines. This would be fairly simple. Changing Creator/Contributor would be more complicated.This is the historical explanation. I'd love to hear more comments about how to proceed in light of developments to date.Margret BranschofskyDSpace User Support ManagerDigital Library Research GroupBldg.
 14S-M24(617)253-1293margretb at mit.eduhttp://dspace.mit.eduAt 02:48 AM 6/21/2004 +0550, dp007 wrote:>hi all,>>dspace recommends not to use the metadata creator and source. it>says "only for harvested metadata". can anyone explain this?>>thanks in advance,>regards,>dp>_______________________________________________>Dspace-general mailing list>Dspace-general at mit.edu>http://mailman.mit.edu/mailman/listinfo/dspace-generalMargret BranschofskyDSpace User Support ManagerDigital Library Research GroupBldg. 14S-M24(617)253-1293margretb at mit.eduhttp://dspace.mit.edu --=====================_267419849==.ALTContent-Type: text/html; charset="us-ascii"DSpace uses the Contributor element instead of the Creatorelement because this relieves the user of the burden of deciding who, ofall the people involved in the production of an item, is "primarilyresponsible" in the creation of the item.  We added roles tocontributor, thinking that was more specific than the vague"creator" field.  So we have
 Contributor. author,Contributor.editor, Contributor.illustrator...etc.  And if anyonewants to leave it vague, they can use the unqualified Contributorfield.Our guide in this decision was the Libraries Application Profile (LAP) ofthe Dublin Core, which was in an early draft stage at the time of DSpacelaunching.  This draft conflated the Contributor and Creatorelements into one. When the DC Libraries Group published the presentdraft of the LAP (officially called DC-Lib), the contributor and creatorelements reappeared as separate elements. However, there is a commentunder both of these elements that states "Creator and Contributormay be conflated if desired by the application".We left Creator in our schema only because we anticipated that we mightin the future harvest metadata that contains values in the Creatorelement, and we wanted to be able to accept that information.As time goes by we see that this decision is proving to be somewhatinconvenient for metadata harvesters.  A!
 s for
 Source, at the time of DSpace launching the LAP (and also theDCMI) were counseling people not to use Source because it had beenmis-used by some applications, in their opinion.    Sincethen I have seen its use being recommended again, so it might be time forus to change that line in our guidelines.  This would be fairlysimple.  Changing Creator/Contributor would be morecomplicated.This is the historical explanation.  I'd love to hear more commentsabout how to proceed in light of developments to date. Margret BranschofskyDSpace User Support ManagerDigital Library Research GroupBldg. 14S-M24(617)253-1293margretb at mit.eduhttp://dspace.mit.eduAt 02:48 AM 6/21/2004 +0550, dp007 wrote:hi all,dspace recommends not to use the metadata creator and source. it says "only for harvested metadata". can anyone explainthis?thanks in advance,regards,dp_______________________________________________Dspace-general mailing
 listDspace-general at mit.eduhttp://mailman.mit.edu/mailman/listinfo/dspace-generalMargret BranschofskyDSpace User Support ManagerDigital Library Research GroupBldg. 14S-M24(617)253-1293margretb at mit.eduhttp://dspace.mit.edu--=====================_267419849==.ALT--------------------------------_______________________________________________Dspace-general mailing listDspace-general at mit.eduhttp://mailman.mit.edu/mailman/listinfo/dspace-generalEnd of Dspace-general Digest, Vol 11, Issue 9*********************************************

---------------------------------
Do you Yahoo!?
Yahoo! Mail - 50x more storage than other providers!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/dspace-general/attachments/20040624/963bef26/attachment.htm