rdm: roadmap update

lnielsen · lnielsen · commit ff8862f5cda7 · 2024-10-23T14:28:35.000+02:00
diff --git a/content/products/rdm/roadmap/access-request/contents.lr b/content/products/rdm/roadmap/access-request/contents.lr
@@ -1,4 +1,4 @@
-column: future
+column: done
 ---
 body:
 
diff --git a/content/products/rdm/roadmap/branded-communities/contents.lr b/content/products/rdm/roadmap/branded-communities/contents.lr
@@ -1,4 +1,4 @@
-column: future
+column: done
 ---
 body: Add support for styling  communities with their own visual identity.
 
diff --git a/content/products/rdm/roadmap/coar-notify/contents.lr b/content/products/rdm/roadmap/coar-notify/contents.lr
@@ -0,0 +1,11 @@
+column: current
+---
+title: COAR Notify for peer-review.
+---
+category: Metadata
+---
+body:
+
+Implement support for receiving peer review notification events via the COAR Notify protocol.
+
+*@Cottage Labs*
diff --git a/content/products/rdm/roadmap/collections/contents.lr b/content/products/rdm/roadmap/collections/contents.lr
@@ -0,0 +1,9 @@
+column: done
+---
+title: Collections: Backend + Browse page
+---
+category: Metadata
+---
+body:
+
+See example on https://zenodo.org/communities/eu/browse
diff --git a/content/products/rdm/roadmap/community-enhancements/contents.lr b/content/products/rdm/roadmap/community-enhancements/contents.lr
@@ -1,4 +1,4 @@
-column: current
+column: done
 ---
 body: Enhance the communities feature with support for:
 
diff --git a/content/products/rdm/roadmap/concept-dois/contents.lr b/content/products/rdm/roadmap/concept-dois/contents.lr
@@ -1,4 +1,4 @@
-column: future
+column: done
 ---
 body:
 
diff --git a/content/products/rdm/roadmap/contents.lr b/content/products/rdm/roadmap/contents.lr
@@ -2,4 +2,4 @@ _model: Products
 ---
 _template: products/rdm/roadmap.html
 ---
-title: InvenioRDM Roadmap
+title: Roadmap
diff --git a/content/products/rdm/roadmap/data-citation-support/contents.lr b/content/products/rdm/roadmap/data-citation-support/contents.lr
@@ -1,4 +1,4 @@
-column: future
+column: done
 ---
 body:
 
diff --git a/content/products/rdm/roadmap/deposit-form-enhancements/contents.lr b/content/products/rdm/roadmap/deposit-form-enhancements/contents.lr
@@ -1,4 +1,4 @@
-column: near-term
+column: done
 ---
 body: Small enhancements to the deposit form to support features currently available
 on Zenodo. This includes adding optional support for:
diff --git a/content/products/rdm/roadmap/export-formats/contents.lr b/content/products/rdm/roadmap/export-formats/contents.lr
@@ -1,4 +1,4 @@
-column: near-term
+column: done
 ---
 body:
 
diff --git a/content/products/rdm/roadmap/github/contents.lr b/content/products/rdm/roadmap/github/contents.lr
@@ -1,4 +1,4 @@
-column: future
+column: done
 ---
 body:
 
diff --git a/content/products/rdm/roadmap/harvesting/contents.lr b/content/products/rdm/roadmap/harvesting/contents.lr
@@ -0,0 +1,10 @@
+column: done
+---
+title: Harevsting of ROR, ORCID.
+---
+category: Metadata
+---
+body:
+
+Recurrent harvesting of ROR and ORCID into the names, affiliations and funders
+vocabulary.
diff --git a/content/products/rdm/roadmap/metadata-checks/contents.lr b/content/products/rdm/roadmap/metadata-checks/contents.lr
@@ -0,0 +1,11 @@
+column: future
+---
+title: Metadata curation checks
+---
+category: Metadata
+---
+body:
+
+Add support for automated basic curation checks of records per community.
+
+*@CERN*
diff --git a/content/products/rdm/roadmap/multipart-upload/contents.lr b/content/products/rdm/roadmap/multipart-upload/contents.lr
@@ -0,0 +1,11 @@
+column: current
+---
+title: Support for multipart file-upload
+---
+category: Files
+---
+body:
+
+Add support for multipart file upload in InvenioRDM.
+
+*@CESNET*
diff --git a/content/products/rdm/roadmap/subcommunities/contents.lr b/content/products/rdm/roadmap/subcommunities/contents.lr
@@ -1,4 +1,4 @@
-column: future
+column: done
 ---
 body: Add support for creating and managing fully featured subcommunities (i.e. support for records, members, settings etc) .
 
diff --git a/content/products/rdm/roadmap/swh/contents.lr b/content/products/rdm/roadmap/swh/contents.lr
@@ -0,0 +1,12 @@
+column: near-term
+---
+title: Software Heritage
+---
+category: Metadata
+---
+body:
+
+Document and launch the Software Heritage integration for use in InvenioRDM. The
+integration is currently launched on Zenodo.
+
+*@CERN*
diff --git a/content/products/rdm/roadmap/usage-statistics/contents.lr b/content/products/rdm/roadmap/usage-statistics/contents.lr
@@ -1,4 +1,4 @@
-column: current
+column: done
 ---
 body: Migrate Zenodo's current usage statistics module providing record views
 and downloads according to COUNTER Code of Practice for Research Data Usage Metrics.
diff --git a/templates/products/rdm/roadmap.html b/templates/products/rdm/roadmap.html
@@ -2,16 +2,21 @@
 
 {% extends "page-rdm.html" %}
 {% block page_title %}{{ this.title }}{% endblock %}
-{% block page_subtitle %}January 2023{% endblock %}
+{% block page_subtitle %}October 2024{% endblock %}
 
 {% block page_body %}
 
 <section class="roadmap-section section-content-light-bg">
   <div class="container">
-    {% include "roadmap-table.html" %}
     <div class="row roadmap-table">
-      <div class="col-sm-4 column">
+      <div class="col-sm-12 column" style="text-align:center">
+      Follow our discussion on features on <a href="https://github.com/inveniosoftware/product-rdm/discussions">GitHub Discussions</a>
       </div>
+    </div>
+    {% include "roadmap-table.html" %}
+    <div class="row roadmap-table">
+      <div class="col-sm-4 column"></div>
+
       <div class="col-sm-4 column">
           <h2 class="section-title">Done 🚀</h2>
           <p>What we have recently completed</p>
@@ -36,28 +41,9 @@ <h2 class="section-title">Release dates</h2>
 
     <div class="container">
       <p>
-        Following is an overview over the upcoming planned releases. For more information, please read our <a href="https://inveniordm.docs.cern.ch/releases/maintenance-policy/" title="InvenioRDM maintenance policy">maintenance policy</a>.
+        We aim to have a major release once a year. For more information, please read our <a href="https://inveniordm.docs.cern.ch/releases/maintenance-policy/" title="InvenioRDM maintenance policy">maintenance policy</a>.
       </p>
-      <div class="road-map-info row">
-
-        <div class="col-sm-6 column">
-          <h3>Long-Term Support (LTS) - production-ready</h3>
-          <p>
-            LTS are releases that can be used for production services. LTS releases are supported with bug and security fixes for minimum 1 year and maximum until 6 months after the next LTS release has been released.
-          </p>
-        </div>
-        <div class="col-sm-6 column">
-          <h3>Short-Term Support (STS)</h3>
-          <p>
-            STS releases should NOT be used for production services. An STS releases is only supported until the next release.
-            STS releases are used to ship new features fast so that the community can provide feedback.
-          </p>
-        </div>
-      </div>
-
     </div>
-
-    {% include "timeline.html" %}
   </div>
 </section>
 
@@ -66,15 +52,6 @@ <h3>Short-Term Support (STS)</h3>
     <h2 class="section-title">FAQ</h2>
     <div class="row">
       <div class="col-md-6">
-        <p>
-          <strong>What are your top priorities?</strong> <br />
-          Our top priorities in the coming period is to migrate Zenodo to InvenioRDM.
-        </p>
-        <p>
-          <strong>When is the roadmap updated?</strong> <br />
-          We update the roadmap roughly every 3 months. The next update is
-          planned for April 2023.
-        </p>
         <p>
           <strong>What does current, near-term and planned mean?</strong> <br />
           <ul>
@@ -100,6 +77,11 @@ <h2 class="section-title">FAQ</h2>
           coming release. We on purpose do not communicate in which
           release a given feature will be shipped.
         </p>
+
+
+      </div>
+
+      <div class="col-md-6">
         <p>
           <strong>Why do you not tie features to release dates?</strong> <br />
           We want to communicate clearly the inherent uncertainty in our planned
@@ -118,47 +100,12 @@ <h2 class="section-title">FAQ</h2>
           and more resilient community, as well as building features that serve
           real needs for our community.
         </p>
-
-      </div>
-
-      <div class="col-md-6">
-        <p>
-          <strong>Is your internal development schedule public?</strong> <br />
-          No. Only InvenioRDM partners have access to the internal development
-          schedule.
-        </p>
-        <p>
-          <strong>Why is the internal development schedule not public?</strong> <br />
-          The public roadmap accurately communicates the uncertaines in the
-          development schedule and ensures we set the proper expectations.
-
-          The internal development schedule on the other is an internal
-          planning tool and therefore does not accurately communicate the
-          inherent uncertaines. The schedule therefore has a high risk of
-          resulting in failed expectations.
-
-          Alternatively, we should communicate features with quite large
-          buffer times, but this would also not accurately communicate the
-          current fast-paced development.
-        </p>
-        <p>
-          <strong>What is the difference between the internal development schedule and the public roadmap?</strong> <br />
-          The only differences between the internal development schedule and the public roadmap
-          is that the internal schedule assigns a feature to a) a release date b) a responsible person c)
-          participating partners and d) a effort estimate.
-        </p>
         <p>
           <strong>Can I use your roadmap to make commitments?</strong> <br />
           Any commitment you make is your own commitment and made at your own risk and
           you must evaluate the impact of not meeting your commitment. If you
           need a specific feature, the best you can do is to help accelerate the roadmap.
         </p>
-        <p>
-          <strong>How can I help accelerate the roadmap?</strong> <br />
-          We will be happy to explore with you, how you can best help accelerate the
-          roadmap. Please get in touch with the Product Manager (<a href="mailto:lars.holm.nielsen@cern.ch">lars.holm.nielsen@cern.ch</a>). Options include anything from contributing developers to contracting
-          out work to other InvenioRDM partners.
-        </p>
       </div>
     </div>
   </div>

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-column: future`
	`1`	`+column: done`
`2`	`2`	`---`
`3`	`3`	`body:`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-column: current`
	`1`	`+column: done`
`2`	`2`	`---`
`3`	`3`	`body: Enhance the communities feature with support for:`
`4`	`4`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,4 @@`
`1`		`-column: near-term`
	`1`	`+column: done`
`2`	`2`	`---`
`3`	`3`	`body: Small enhancements to the deposit form to support features currently available`
`4`	`4`	`on Zenodo. This includes adding optional support for:`