Hi Hendrik,

What you are likely seeing is the fact that, in DSpace 7, we don't yet have
all the submission/workflow functionality merged/completed (quite yet,
though we are getting closer).

As of this moment, the basic REST API features for that "submission wizard"
functionality are available on the "master" branch (at
https://github.com/DSpace/DSpace/). However, the actual User Interface
portion is still being worked on within this (large) Pull Request:
https://github.com/DSpace/dspace-angular/pull/279

This DSpace 7 submission functionality *does* include import of metadata
from existing sources.  However, the code uses the BTE import framework
described here:
https://wiki.duraspace.org/pages/viewpage.action?pageId=68064788  This BTE
import framework already does support arXiv and PubMed.

To be fair, this is a slight change in direction from what we initially
anticipated.  In the DSpace 6 documentation, we still have a note that says
the BTE framework is "deprecated" in favor of the "2016 Framework for live
import from external sources".  However, that deprecation may need to be
reconsidered *unless* we find a way to quickly update the "2016 Framework"
to full compatibility with the BTE framework.

So, this is all to say, if you are still interested in enhancing the 2016
framework, I'd encourage you to start by creating a PR (or two) for
review/testing.  This 2016 framework *still exists* in the DSpace 7
codebase -- most of the DSpace 7 Java backend is still the same as the
DSpace 6 backend (except we've updated some dependencies in various
areas).  So, any code you have that works on DSpace 6 should be relatively
easy to port to DSpace 7.

If you need more advice, please feel free to ask on this mailing list. We'd
definitely appreciate any help on DSpace 7 efforts, as our DSpace 7 team is
still rather small overall.  With extra help, there's more we can achieve
together.

- Tim


On Fri, Nov 9, 2018 at 10:39 AM Hendrik Geßner <heng...@gmail.com> wrote:

> Dear developers,
>
> we installed DSpace 6.x at our institute and implemented an arXiv provider
> for the "2016 Framework for live import from external sources" (
> https://wiki.duraspace.org/display/DSDOC6x/2016+Framework+for+live+import+from+external+sources)
> which we want to give back to the community. As far as I understand there's
> a feature freeze for DSpace 6, new features can only be added to DSpace 7.
> I'm willing to port our arXiv code to the DSpace 7 code base, but it seems
> that the framework isn't even integrated yet.
>
> We discussed this issue internally and I was given permission to port the
> DSpace 6 "2016 Framework for live import from external sources" to DSpace 7
> in my work time. Unfortunately, this doesn't seem to be as straightforward
> as I would have expected and I'm still a bit confused. Can you please help
> me in understanding the following issues?
>
>    - I could not find a roadmap entry for porting the existing framework
>    to DSpace 7, did I miss something?
>    - In DSpace 7 the whole import process seems to be tied to a new
>    submission wizard (
>    https://wiki.duraspace.org/display/DSPACE/Submission+wizard), yet
>    there doesn't seem to be a consensus yet. Is this right?
>    - Is there any plan to have a user-driven import of metadata from
>    existing sources, namely arXiv, PubMed etc.?
>
> I'm still motivated to give the arXiv code back, but I think I need a bit
> more guidance on where to start.
>
> Kind regards,
> Hendrik Geßner
>
> --
> All messages to this mailing list should adhere to the DuraSpace Code of
> Conduct: https://duraspace.org/about/policies/code-of-conduct/
> ---
> You received this message because you are subscribed to the Google Groups
> "DSpace Developers" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to dspace-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to dspace-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/dspace-devel.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
Tim Donohue
Technical Lead for DSpace & DSpaceDirect
DuraSpace.org | DSpace.org | DSpaceDirect.org

-- 
All messages to this mailing list should adhere to the DuraSpace Code of 
Conduct: https://duraspace.org/about/policies/code-of-conduct/
--- 
You received this message because you are subscribed to the Google Groups 
"DSpace Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to dspace-devel+unsubscr...@googlegroups.com.
To post to this group, send email to dspace-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/dspace-devel.
For more options, visit https://groups.google.com/d/optout.

Reply via email to