Hi all, I'm not even sure of the right question to ask here, but I've been lumped with this task, so here it is.
We are using DSpace 4.1 on RHEL 6. We are evaluating the Ebsco Discovery Service (EDS) at our Library, and want to include results from our DSpace repository. These can be harvested, but in the advanced search section of the EDS interface, you can limit to a repository "collection". Currently EDS uses ListSets to list *every* collection in our repository, which creates a list that is way too long. Is there a way I can expose just the top level communities through OAI (see the list of Communities on the home page of http://ses.library.usyd.edu.au/) eg. custom OAI sets? The instructions EBSCO have given me are below for reference - I'm having trouble deciphering Option 2 but I don't think it's the way we want to go if possible. Any advice would be very much appreciated! Thanks, Gary ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Can you clarify how we should update the collection limiters to be set up for your IR database? You can either, *1) use setSpec/setName pairs (ListSets parameter in the OAI URL: http://ses.library.usyd.edu.au/oai/request?verb=ListSets <http://ses.library.usyd.edu.au/oai/request?verb=ListSets>) to make limiters. * OR *2) create a Collection Name Lookup Table.* If your data is harvested via OAI, the <setName> in the sets.xml file will be used to construct the Collection Name. If your data does not contain sets, which metadata element contains the Collection Name? If there are no collection names, please indicate that here: To ensure your Collection Names are appropriately indicated and displayed, please submit a lookup table that we can use to map the formats present in your data set using the Collection Name(s) given in the dataset and indicate what should be displayed under the Collection facet, Collection limiters, and on the Full Record display: *Name_in_data* –- the text in the designated metadata element (typically the <setSpec> value) that we should use for matching to the lookup *Facet_Display* -- values should be concise versions of the full name, with a maximum of approx. 40 characters. (It is neater on the interface than an extended title). This value will be phrase indexed and will search exactly that set. *Full_Display* -- the full name of your collection or set, as you would like it to appear on the full record. Will be word indexed. *Limiter_group* –- the visible limiter string that will search one or more facet values. In the example below you could have one limiter value per facet, or group together under a larger set. *Example:* Collection Name Lookup Table [image: http://www.tfaforms.com/forms/get_image/160593/d56da49b6d9404f0071da6b2a3b92afc-lookup.PNG] Once we get more information from you, we can update the collection limiters. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
