Versions Compared

Old Version 6

changes.mady.by.user Pascal-Nicolas Becker

Saved on

compared with

New Version Current

changes.mady.by.user Andrea Bollini (4Science)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: integrate discussion notes about different development speed differences between dspace and dspace-cris

...

  • Agustina summarized last week's discussion highlights:
    • Limited work is needed to bring the communities together
    • There was also a point around a more inclusive governance structure, take into account smaller, less powerful institutions; this is an opportunity to take their voices into account
    • Take into account the extended use cases
    • Flexible, turn-key DSpace vs modularization 
    • Getting deeper understanding what DSpace CRIS is and try to reassure the community, focusing on the features so they know better
    • Wider issue around increased complexity of DSpace over time, trying to find ways to control this 
  • Last meeting: suggestion to come up with focus groups; feeling that its adding too much structure and too much overhead
    • If assumption is right that most features are needed anyways in DSpace, we can continue with the structure 
    • General feeling is that the community is one; thing that majorly changes is shaping the releases 
    • The Library Code was asked by a client to recode the cover page on items; this is turned off by default in most repos because of conflicts with Google Scholar; point is: there are already features that are switched off by default that are niche features in DSpace
      • We just need to define: which functionality in DSpace or DSpace-CRIS are deprecated? Which are needed? All depends on list of features
  • Pierre expressed that to him, these are two completely different systems; there may be overlap, convergence of functionality of DSpace with CRIS systems; what kind of features that are clearly meant for CRIS would be brought to the community? It does have consequences. What would be the specific CRIS needs that will be brought into DSpace in the way we prioritize things?
  • What is a repo? digital objects plus metadata; What is a CRIS system? A system that collects metadata about certain objects, less files
    • It comes down to managing metadata and connecting entities 
    • CRIS gives more tools do deal with the flexibility of configurable entities
    • There is more security - there is more personal data
    • Need to have hierarchical metadata
    • There is nothing specific of a funding process - not a funding system; DSpace provides the infrastructure to do this stuff
  • DSpace CRIS users are very few institutions that are not research output producing institutions - significant subset of DSpace users base
    • DSpace has been growing in terms of use cases, geographical locations
    • Example: multilingual - great feature
      • How are we going to deal with this? Are we going to focus on DSpace? 
      • Difference between CRIS and DSpace: CRIS makes better use of the possibility in which language a certain metadata field is being filled out 
      • Main question is: how do we deal with DSpace opening up to other users and use cases, outside of what is the dominant use case today? How do change governance so that we can make DSpace more usable for more use cases?
  • One of the most important questions: why do we want to do this merger, because . Because CRIS seems to be a completely different system; ? needs to be communicated
    • There are also CRIS users that use CRIS as a repository - why?
  • Merger of DSpace and DSpace-CRIS is not about restructuring the community
    • There is no feature to the best of Andrea's knowledge that only serves DSpace-CRIS and couldn't serve DSpace
  • CRIS can Lieven pointed out that CRIS has been able to move much faster , it's much than DSpace because it was simpler for them 4Science to implement features without the community-led review process. Andrea disagrees and explains that DSpace-CRIS moves faster as it was built on the foundation of a simpler and more effective way to manage relations that were already there before DSpace 7. In this way, 4Science was able to dedicate time that DSpace is devoting to reimplement and refine such things to implement and enhance features needed to allow entities to be used in real-world scenarios.
  • Many agree that 
    • PRs are too cumbersome, we are not good enough with reviews, we are not good enough with helping out, these issues need to be brought again to Steering
    • the code base of DSpace is getting larger and more and more complex. How can we move fast enough? How can we make PRs easy to make and to review? Is that a topic of the merger or a general topic or a general topic that is becoming more difficult due to the merger?  

Next meeting

  • Continue discussion; work towards list of features

...