Merge pull request creativecommons#734 from creativecommons/dataviz-note

Add note to dataviz project blog posts

Author: TimidRobot

content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr

@@ -31,7 +31,7 @@ En las versiones pasadas de estos programas tuvimos excelentes resultados llevad
 - [CC Search Browser extension](https://github.com/creativecommons/ccsearch-browser-extension) por Mayank Nader
 - [CC Vocabulary](https://github.com/creativecommons/vue-vocabulary) por Dhruv Bhanushali
 - [Revamping the CC Chooser](https://github.com/creativecommons/cc-chooser) por Ari Madian
-- [CC Catalog Data Visualization](https://github.com/creativecommons/cccatalog-dataviz) por Maria Belen Guaranda
+- [CC Catalog Data Visualization](https://github.com/cc-archive/cccatalog-dataviz) por Maria Belen Guaranda
 
 ## Outreachy 2019-2020
 - [Improve License Chooser](https://github.com/creativecommons/cc-chooser) por Olga Bulat

content/blog/entries/2020-12-07-upcoming-changes-to-community/contents.lr

@@ -68,7 +68,7 @@ The following projects are entering maintenance mode. The services will remain o
 -   [CC Catalog](https://github.com/creativecommons/cccatalog)
 -   [CC Catalog API](https://github.com/creativecommons/cccatalog-api)
 -   [CC Search](https://github.com/creativecommons/cccatalog-frontend/)
--   [Linked Commons](https://github.com/creativecommons/cccatalog-dataviz/)
+-   [Linked Commons](https://github.com/cc-archive/cccatalog-dataviz/)
 
 Catalog, API, and Linked Commons contributors are encouraged to contribute  to our other Python projects such as the [CC Legal Database](https://github.com/creativecommons/legaldb) or the upcoming [CC Licenses](https://github.com/creativecommons/cc-licenses) project. If you are a CC Search contributor, we recommend checking out frontend projects such as the [CC Chooser](https://github.com/creativecommons/chooser) or [Vocabulary](https://github.com/creativecommons/vocabulary).
 

content/blog/entries/cc-datacatalog-data-processing-2/contents.lr

@@ -16,6 +16,11 @@ pub_date: 2019-07-26
 ---
 body:
 
+> ℹ️ **2023-08-31:** This project was archived along with the shuttering of CC
+Search (now [Openverse](https://openverse.org/)). Please also see the
+[Quantifying the Commons](https://github.com/creativecommons/quantifying)
+project.
+
 This is a continuation of my last blog post about the data processing part of the CC-data catalog visualization project. I recommend you to read that [last post](https://opensource.creativecommons.org/blog/entries/cc-datacatalog-data-processing/) for a better understanding of what I'll explain here.
 
 
@@ -68,7 +73,7 @@ The thresholds for the quantity of images and links are my intuitions from havin
 - Visualization with the data. 
 - Development or modification of pruning/filtering rules.
 
-You can follow the project development in the [Github repo](https://github.com/creativecommons/cccatalog-dataviz).
+You can follow the project development in the [Github repo](https://github.com/cc-archive/cccatalog-dataviz).
 
 CC Data Catalog Visualization is my GSoC 2019 project under the guidance of [Sophine
 Clachar](https://creativecommons.org/author/sclachar/), who has been greatly helpful and considerate since the GSoC application period. Also, my backup mentor, [Breno Ferreira](https://creativecommons.org/author/brenoferreira/), and engineering director [Kriti

content/blog/entries/cc-datacatalog-data-processing-3/contents.lr

@@ -16,6 +16,11 @@ pub_date: 2019-08-12
 ---
 body:
 
+> ℹ️ **2023-08-31:** This project was archived along with the shuttering of CC
+Search (now [Openverse](https://openverse.org/)). Please also see the
+[Quantifying the Commons](https://github.com/creativecommons/quantifying)
+project.
+
 This is a continuation of my last blog post about the data processing part 2 of the CC-data catalog visualization project. I recommend you to read that [last post](https://opensource.creativecommons.org/blog/entries/cc-datacatalog-data-processing-2/) for a better understanding of what I'll explain here.
 
 Hello! In this post I am going to talk you about the extraction of unique nodes, and links, and the visualization of the force-directed graph with the processed data. 
@@ -56,7 +61,7 @@ The other tasks left to do are:
 - Visualization of the pie chart
 - Development or modification of pruning/filtering rules.
 
-You can follow the project development in the [Github repo](https://github.com/creativecommons/cccatalog-dataviz).
+You can follow the project development in the [Github repo](https://github.com/cc-archive/cccatalog-dataviz).
 
 CC Data Catalog Visualization is my GSoC 2019 project under the guidance of [Sophine
 Clachar](https://creativecommons.org/author/sclachar/), who has been greatly helpful and considerate since the GSoC application period. Also, my backup mentor, [Breno Ferreira](https://creativecommons.org/author/brenoferreira/), and engineering director [Kriti

content/blog/entries/cc-datacatalog-data-processing/contents.lr

@@ -16,6 +16,11 @@ pub_date: 2019-07-10
 ---
 body:
 
+> ℹ️ **2023-08-31:** This project was archived along with the shuttering of CC
+Search (now [Openverse](https://openverse.org/)). Please also see the
+[Quantifying the Commons](https://github.com/creativecommons/quantifying)
+project.
+
 Welcome to the data processing part of the GSoC project! In this blog post, I am going to tell you about my first thoughts with the real data, and give you some details of the implementation developed so far. 
 
 ### Data Extraction
@@ -67,7 +72,7 @@ Another important aspect is the licenses types. In the dataset, we do not have t
 - Data aggregation
 - Visualization with the data + perfectioning pruning/filtering rules
 
-You can follow the project development in the [Github repo](https://github.com/creativecommons/cccatalog-dataviz).
+You can follow the project development in the [Github repo](https://github.com/cc-archive/cccatalog-dataviz).
 
 CC Data Catalog Visualization is my GSoC 2019 project under the guidance of [Sophine
 Clachar](https://creativecommons.org/author/sclachar/), who has been greatly helpful and considerate since the GSoC application period. Also, my backup mentor, [Breno Ferreira](https://creativecommons.org/author/brenoferreira/), and engineering director [Kriti

content/blog/entries/cc-datacatalog-data-thelinkedcommons/contents.lr

@@ -16,6 +16,11 @@ pub_date: 2019-09-03
 ---
 body:
 
+> ℹ️ **2023-08-31:** This project was archived along with the shuttering of CC
+Search (now [Openverse](https://openverse.org/)). Please also see the
+[Quantifying the Commons](https://github.com/creativecommons/quantifying)
+project.
+
 This is a continuation of my last blog post about the data processing part 3 of the CC-data catalog visualization project. I recommend you to read that [last post](https://opensource.creativecommons.org/blog/entries/cc-datacatalog-data-processing-3/) for a better understanding of what I'll explain here.
 
 Hello! In this last post, I am going to talk you about the final visualization. First, I would like to talk about the data and share my recommendations.
@@ -87,7 +92,7 @@ Here is the final visualization, using a sample data from one month of the Commo
 <br>
 
 
-You can check the whole project source code in the [Github repo](https://github.com/creativecommons/cccatalog-dataviz/tree/master/GSoC2019). 
+You can check the whole project source code in the [Github repo](https://github.com/cc-archive/cccatalog-dataviz/tree/master/GSoC2019). 
 
 ### Final comments and future work
 This was my first experience with big data visualization, and I really enjoyed it!

content/blog/entries/cc-datacatalog-visualization/contents.lr

@@ -16,6 +16,11 @@ pub_date: 2019-06-17
 ---
 body:
 
+> ℹ️ **2023-08-31:** This project was archived along with the shuttering of CC
+Search (now [Openverse](https://openverse.org/)). Please also see the
+[Quantifying the Commons](https://github.com/creativecommons/quantifying)
+project.
+
 _“By visualizing information, we turn it into a landscape that you can explore with your eyes.”_ – David McCandless.
 
 The landscape of licensed content is wide and varied. We have domains linking to other domains, different license types, and some metadata. This information is extracted from the Internet monthly by [Common Crawl](http://commoncrawl.org/). It is fair to mention that we have 250 million works and growing! If you didn't know we had so much licensed content, well then, this is one of the goals of this project: show the users how licensers are connected, their licensed content, and show how the licensing wave is expanding.
@@ -73,7 +78,7 @@ As the front-end is complete, I am going to get my hands dirty with the data. Fu
 - Reviewing of part of the dataset
 - Implementation of a module for cleaning and parsing the data
 
-You can follow the project development in the [Github repo](https://github.com/creativecommons/cccatalog-dataviz).
+You can follow the project development in the [Github repo](https://github.com/cc-archive/cccatalog-dataviz).
 
 CC Data Catalog Visualization is my GSoC 2019 project under the guidance of [Sophine
 Clachar](https://creativecommons.org/author/sclachar/), who has been greatly helpful and considerate since the GSoC application period. Also, my backup mentor, [Breno Ferreira](https://creativecommons.org/author/brenoferreira/), and engineering director [Kriti

content/blog/entries/linked-commons-autocomplete-feature/contents.lr

@@ -78,4 +78,4 @@ Here are some aggregated result statistics.
 In the next blog, we will be covering the long awaited data update and the new architecture.
 
 ## Conclusion
-Overall, I enjoyed working on this feature and it was a great learning experience. This feature has been successfully integrated to the development version, do check it out. Now that you have read this blog till the end, I hope that you enjoyed it. For more information please visit our [Github repo](https://github.com/creativecommons/cccatalog-dataviz/). We are looking forward to hearing from you on linked commons. Our [slack](https://creativecommons.slack.com/channels/cc-dev-cc-catalog-viz) doors are always open to you, see you there. :)
+Overall, I enjoyed working on this feature and it was a great learning experience. This feature has been successfully integrated to the development version, do check it out. Now that you have read this blog till the end, I hope that you enjoyed it. For more information please visit our [Github repo](https://github.com/cc-archive/cccatalog-dataviz/). We are looking forward to hearing from you on linked commons. Our [slack](https://creativecommons.slack.com/channels/cc-dev-cc-catalog-viz) doors are always open to you, see you there. :)

content/blog/entries/linked-commons-data-update/contents.lr

@@ -83,7 +83,7 @@ This small change in the design simplified a lot of things, and now the new grap
 
 ## Conclusion
 
-This task was really challenging and I learnt a lot. It was really mesmerizing to see the **Linked Commons grow and evolve**. I hope you enjoyed reading this blog. You can follow the project development [here](https://github.com/creativecommons/cccatalog-dataviz/), and access the stable version of linked commons [here](http://dataviz.creativecommons.engineering/). 
+This task was really challenging and I learnt a lot. It was really mesmerizing to see the **Linked Commons grow and evolve**. I hope you enjoyed reading this blog. You can follow the project development [here](https://github.com/cc-archive/cccatalog-dataviz/), and access the stable version of linked commons [here](http://dataviz.creativecommons.engineering/). 
 
 Feel free to report bugs and suggest features. It will help us improve this project. If you wish to join the our team, consider joining our [slack](https://creativecommons.slack.com/channels/cc-dev-cc-catalog-viz) channel. Read more about our community teams [here](https://opensource.creativecommons.org/community/). See you in my next blog! 🚀
 ___

content/blog/entries/linked-commons-gsoc-wrap-up/contents.lr

@@ -75,19 +75,19 @@ Description: Returns a set of nodes which contains the {query} pattern in their
 
 ### My Code Contributions
 
-**Repository:** https://github.com/creativecommons/cccatalog-dataviz/
+**Repository:** https://github.com/cc-archive/cccatalog-dataviz/
 
-**Commits:** https://github.com/creativecommons/cccatalog-dataviz/commits/master
+**Commits:** https://github.com/cc-archive/cccatalog-dataviz/commits/master
 
-**Contributors:** https://github.com/creativecommons/cccatalog-dataviz/graphs/contributors
+**Contributors:** https://github.com/cc-archive/cccatalog-dataviz/graphs/contributors
 
 
-[**Migrate frontend to React #28**](https://github.com/creativecommons/cccatalog-dataviz/pull/28)
+[**Migrate frontend to React #28**](https://github.com/cc-archive/cccatalog-dataviz/pull/28)
 - Migrated the frontend to a web application using React.js for smooth rendering performance.
 - Add client-side graph filtering method to enable users to interact with the loaded graph.
 
 
-[**Add server-side filtering #29**](https://github.com/creativecommons/cccatalog-dataviz/pull/29)
+[**Add server-side filtering #29**](https://github.com/cc-archive/cccatalog-dataviz/pull/29)
 - We realized that the client-side graph filtering method is not very scalable. This PR adds the basic structure for the backend server and adds server-side graph filtering logic.
 - Added a parser to convert the input JSON file from `{nodes:[], links:[]}` schema to the distance list format. 
 
@@ -100,7 +100,7 @@ Description: Returns a set of nodes which contains the {query} pattern in their
 
 
 
-[**Design upgrade #33**](https://github.com/creativecommons/cccatalog-dataviz/pull/33)
+[**Design upgrade #33**](https://github.com/cc-archive/cccatalog-dataviz/pull/33)
 - It revamped the design of the frontend.
 - Added both primary light theme and secondary dark theme
 
@@ -111,24 +111,24 @@ Description: Returns a set of nodes which contains the {query} pattern in their
     </figure>
 </div>
 
-[**Add node suggestions feature #35**](https://github.com/creativecommons/cccatalog-dataviz/pull/35)
+[**Add node suggestions feature #35**](https://github.com/cc-archive/cccatalog-dataviz/pull/35)
 - Added query autocomplete feature, to enable users to explore all the nodes in the database.
 - This functionality aims to minimize the number of misspelt filtering tries from the client. 
 - Refer to [this blog](/blog/entries/linked-commons-autocomplete-feature/) for the motivation and detailed report on why we added autocomplete aka node suggestions feature.
 
 
-[**Fix filtering module #38**](https://github.com/creativecommons/cccatalog-dataviz/pull/38)
+[**Fix filtering module #38**](https://github.com/cc-archive/cccatalog-dataviz/pull/38)
 - Optimizes the build-dB-script to run efficiently on the larger and newer dataset of the cc-catalog.
 - Added the basic form of the randomized graph filtering method.
 - Refer to [this blog](/blog/entries/linked-commons-data-update/) for a piece of detailed information on data update.
 
 
-[**Database upgrade and core enhancements #39**](https://github.com/creativecommons/cccatalog-dataviz/pull/39)
+[**Database upgrade and core enhancements #39**](https://github.com/cc-archive/cccatalog-dataviz/pull/39)
 - It upgrades the primary database from shelve to MongoDB for higher performance.
 - Dockerizes the frontend and backend for both dev and prod environments for higher application portability.
 
 
-[**Frontend enhancements #40**](https://github.com/creativecommons/cccatalog-dataviz/pull/40)
+[**Frontend enhancements #40**](https://github.com/cc-archive/cccatalog-dataviz/pull/40)
 - Fixes common UI bugs, updates the frontend design and enhances the mobile and smaller devices experience with the linked commons
 - Modularizes and updates the code documentation