Date: Fri, 29 Mar 2024 07:14:38 -0400 (EDT) Message-ID: <684312324.30280.1711710878262@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_30279_136155611.1711710878262" ------=_Part_30279_136155611.1711710878262 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
This call is a Community Forum call: Sharing best practices and chal= lenges in the use of existing DSpace features
We will use the international conference call dial-in. Please follow dir= ections below.
Bring your questions/comments you would like to discuss to the call, or = add them to the comments of this meeting page.
If you can join the call, or are willing to comment on the topics submit= ted via the meeting page, please add your name, institution, and repository= URL to the Call Attendees section below.
Popular harvesting and ingesting technologies in DSpace include the OAI-= PMH, OAI-ORE and SWORD protocol.
Throughout the call participants emphasized ways of automating ingest an= d harvesting in DSpace. Popular platforms from which content is harvested f= rom, or ingested into DSpace (or the other way around) include Symplectic E= lements, BioMed Central, and Proquest.
In many cases participants decided to use workflows to assure content qu= ality. Such workflows were primarily used when content is ingested in DSpac= e. In some cases attendees also had a workflow in the other direction. This= is, before harvesters would be able to harvest content from their reposito= ry it would first have to go through an internal workflow in DSpace.
Some participants had their repository harvested by a national platform,= usually through the OAI-PMH and OAI-ORE protocol. Such national harvesters= were usually put into place for funding purpose, so governmental instances= could check on the executed (funded) research.