Build of r/14.x from Mon Oct 30 16:36:27 UTC 2023

r/14.x/admin/index.html

@@ -804,5 +804,5 @@ <h2 id="release-documentation">Release Documentation</h2>
 </html>
 <!--
 MkDocs version : 1.5.3
-Build Date UTC : 2023-10-27 14:25:20.513895+00:00
+Build Date UTC : 2023-10-30 16:36:14.154870+00:00
 -->

r/14.x/admin/modules/youtubepublication/index.html

@@ -37,7 +37,7 @@
               {title: "Before you start", url: "#before-you-start" },
               {title: "Google Developers Configuration", url: "#google-developers-configuration" },
               {title: "YouTube configuration in Opencast", url: "#youtube-configuration-in-opencast" },
-              {title: "Activate YouTube publication in Opencast", url: "#activate-youtube-publication-in-opencast" },
+              {title: "Add YouTube publication to your Opencast workflows", url: "#add-youtube-publication-to-your-opencast-workflows" },
           ]},
         ];
 
@@ -94,32 +94,42 @@ <h2 id="before-you-start">Before you start</h2>
 <p>You need to meet these requirements to make a YouTube Publication:</p>
 <ul>
 <li>Google Account</li>
-<li>YouTube Channel to make the publication</li>
+<li>YouTube Channel to publish to</li>
 </ul>
 <h2 id="google-developers-configuration">Google Developers Configuration</h2>
 <p>Below is a summarized version of <a href="https://developers.google.com/youtube/registering_an_application">Google's quickstart page</a>.  If these
 instructions do not work for you, or are unclear please let us know - Google has a habit of changing its configuration
 pages and we don't always notice!</p>
 <h3 id="create-new-google-project">Create new Google Project</h3>
 <ul>
-<li>Login to Google account</li>
+<li>Login to your Google account</li>
 <li>Navigate to the <a href="https://console.developers.google.com/project"><strong>Google Developers Console</strong></a></li>
 <li>Click <strong>Create Project</strong> and follow the instructions</li>
 <li>Navigate to the <a href="https://console.developers.google.com/apis/credentials"><strong>Google Credentials Console</strong></a></li>
 <li>Select <strong>OAuth consent screen</strong></li>
-<li>Configure the API Consent Screen, you will need to set the Product name</li>
+<li>Configure the API Consent Screen<ul>
+<li>For <strong>User type</strong> select <code>external</code></li>
+<li>Add a test user (only necessary if your app is still in testing mode)</li>
+<li>Fill in the rest of the required settings at discretion</li>
+</ul>
+</li>
 <li>Select <strong>Credentials</strong></li>
-<li>Select <strong>Create Credentials</strong>, specifically OAuth Client ID</li>
-<li>Select <strong>Other</strong> application type</li>
+<li>Select <strong>Create Credentials</strong>, specifically OAuth Client ID<ul>
+<li><strong>Application type</strong> must be set to <code>Desktop</code></li>
+</ul>
+</li>
 </ul>
 <h3 id="save-client-id-in-json-format">Save Client ID in JSON Format</h3>
 <ul>
+<li>Select <strong>Credentials</strong>, you should see a new entry in the <strong>OAuth 2.0 Client IDs</strong> table</li>
 <li>Download the client information in JSON format by clicking <strong>Download JSON</strong><ul>
 <li>This currently looks like an arrow pointing downwards on the rightmost portion of the client id row</li>
 </ul>
 </li>
 <li>Save the JSON file to <code>${karaf.etc}/youtube-v3/client-secrets-youtube-v3.json</code> (Usually this is
-  <code>etc/youtube-v3/client-secrets-youtube-v3.json</code>)</li>
+  <code>etc/youtube-v3/client-secrets-youtube-v3.json</code>). It should match the path configured for
+  <code>org.opencastproject.publication.youtube.clientSecretsV3</code> in
+  <code>org.opencastproject.publication.youtube.YouTubeV3PublicationServiceImpl.cfg</code>.</li>
 </ul>
 <h3 id="enable-api">Enable API</h3>
 <ul>
@@ -136,7 +146,7 @@ <h2 id="youtube-configuration-in-opencast">YouTube configuration in Opencast</h2
 <p>With the JSON file created and saved previously, you have to proceed as described:</p>
 <ul>
 <li>
-<p>Start Opencast server (Restart Opencast in case was running)</p>
+<p>Start Opencast server (Restart Opencast in case it was running)</p>
 <p><strong>Note:</strong> Until this service is fully configured, Opencast will not start completely. In case you
 want to abort the configuration, you only need to delete the JSON file and restart Opencast.</p>
 </li>
@@ -163,38 +173,12 @@ <h2 id="youtube-configuration-in-opencast">YouTube configuration in Opencast</h2
 <p>Restart Opencast</p>
 </li>
 </ul>
-<h2 id="activate-youtube-publication-in-opencast">Activate YouTube publication in Opencast</h2>
-<p>Opencast can now publish to YouTube. The last step is to activate this feature. For this you have to create a new
-workflow or modify an existing one.</p>
-<ul>
-<li>
-<p>Open the workflows <code>etc/opencast/workflows/ng-schedule-and-upload.xml</code> and <code>etc/opencast/workflows/ng-publish.xml</code></p>
-</li>
-<li>
-<p>In the file, modify the <code>&lt;configuration_panel&gt;</code> and enable the YouTube option, like this:</p>
-<pre><code>&lt;input id="publishToYouTube" name="publishToYouTube" type="checkbox" class="configField" value="true"
-       disabled="disabled" /&gt;
-</code></pre>
-</li>
-</ul>
-<p>becomes</p>
-<pre><code>    &lt;input id="publishToYouTube" name="publishToYouTube" type="checkbox" class="configField" value="true"/&gt;
-</code></pre>
-<ul>
-<li>
-<p>Open the workflows <code>etc/opencast/workflows/ng-retract.xml</code></p>
-</li>
-<li>
-<p>In the file, modify the <code>&lt;configuration_panel&gt;</code> and enable the YouTube option, like this:</p>
-<pre><code>&lt;input id="retractFromYouTube" type="checkbox" class="configField" value="true" disabled="disabled" /&gt;
-</code></pre>
-</li>
-</ul>
-<p>becomes</p>
-<pre><code>    &lt;input id="retractFromYouTube" type="checkbox" checked="checked" class="configField" value="true" /&gt;
-</code></pre>
-<p>Opencast will detect the new workflow without restart, with that you can select the new workflow with the YouTube option
-enabled.</p>
+<h2 id="add-youtube-publication-to-your-opencast-workflows">Add YouTube publication to your Opencast workflows</h2>
+<p>Opencast can now publish to YouTube. To make use of this, add the <a href="../../workflowoperationhandlers/publish-youtube-woh/">Publish YouTube workflow operation</a>
+to your Opencast workflows. You can find more details on how to use the operation on its <a href="(../workflowoperationhandlers/publish-youtube-woh.md)">own page</a>.
+In general, it should be placed near your other <code>publish</code> operations.</p>
+<p>You may also want to add the <a href="../../workflowoperationhandlers/retract-youtube-woh/">Retract YouTube workflow operation</a> 
+near your <code>retract</code> operations.</p>
 
   <br>
 

r/14.x/admin/workflowoperationhandlers/publish-youtube-woh/index.html

@@ -90,10 +90,10 @@
     <h1 id="publish-youtube-workflow-operation">Publish YouTube Workflow Operation</h1>
 <p>ID: <code>publish-youtube</code></p>
 <h2 id="description">Description</h2>
-<p>The publish YouTube operation publishes a single stream to YouTube.  This stream must meet YouTube's format
-requirements, and may consist of audio and/or video.  If you want to publish both your presenter and presentation
+<p>The publish YouTube operation publishes a single stream to YouTube. This stream must meet YouTube's format
+requirements, and may consist of one audio and/or video stream. If you want to publish both your presenter and presentation
 streams we suggest using the <a href="../composite-woh/">Composite</a> workflow operation handler to prepare a composite file
-with both streams inside of it.  The default Opencast workflow prepares a video using this method.</p>
+with both streams inside of it.  </p>
 <h2 id="parameter-table">Parameter Table</h2>
 <table>
 <thead>

r/14.x/admin/workflowoperationhandlers/retract-youtube-woh/index.html

@@ -90,7 +90,7 @@ <h1 id="retract-youtube-workflow-operation">Retract Youtube Workflow Operation</
 <p>ID: <code>retract-youtube</code></p>
 <h2 id="description">Description</h2>
 <p>The retract YouTube operation retracts the published elements from YouTube.
-There are no configuration keys at this time.</p>
+There are no configuration keys.</p>
 <h2 id="operation-example">Operation Example</h2>
 <pre><code class="language-xml">&lt;operation
   id=&quot;retract-youtube&quot;

r/14.x/commit

@@ -1,33 +1,5 @@
-commit f9de2789a0039bb915896325eeb16dd68f899da0
-Author: Katrin Ihler <ihler@elan-ev.de>
-Date:   Fri Oct 27 16:24:46 2023 +0200
+commit 910127b85f9b7af978f4367c525f1cdf2dc124d2
+Author: Lars Kiesow <lkiesow@uos.de>
+Date:   Mon Oct 30 17:35:25 2023 +0100
 
-    Fix/improve parts of the Tobira harvest API (subtitles & duration) (#5345)
-
-    Fixes https://github.com/elan-ev/tobira/issues/960
-    Fixes https://github.com/elan-ev/tobira/issues/884
-
-    Look at the commits for more information.
-
-    Note: I was not able to test with events that actually contain
-    subtitles! Since @KatrinIhler asked for this (for Bern), it would be
-    very very cool if you could test this. In particular, whether it fixes
-    the issue you had.
-
-    And if @Arnei has time to take a look at this, I'd be interested in
-    whether you see any problems with my "find subtitles" logic (second
-    commit).
-
-    ### Your pull request should…
-
-    * [ ] have a concise title
-    * [ ] [close an accompanying
-    issue](https://help.github.com/en/articles/closing-issues-using-keywords)
-    if one exists
-    * [ ] [be against the correct
-    branch](https://docs.opencast.org/develop/developer/development-process#acceptance-criteria-for-patches-in-different-versions)
-    * [ ] include migration scripts and documentation, if appropriate
-    * [ ] pass automated tests
-    * [ ] have a clean commit history
-    * [ ] [have proper commit messages (title and body) for all
-    commits](https://medium.com/@steveamaza/e028865e5791)
+    Merge r/13.x into r/14.x

r/14.x/developer/index.html

@@ -403,5 +403,5 @@ <h1 id="opencast-development-guides">Opencast Development Guides</h1>
 </html>
 <!--
 MkDocs version : 1.5.3
-Build Date UTC : 2023-10-27 14:25:22.741833+00:00
+Build Date UTC : 2023-10-30 16:36:16.027524+00:00
 -->