List of selected Dataverse features and possible solution in CKAN Note that CKAN has a lot of feature that other software such as Dataverse may not provide at all. This list only considers an option where a project should be migrated from Dataverse to CKAN so that we can keep existing features while adding/enhancing project with new functionalities available in CKAN out of the box. Dataverse CKAN Support for FAIR Data Principles Yes Data citation for datasets and files

Program_DateAdded - our calculated field to understand when a page was added to a program. Program_DateIncluded - based on publish date of a dataset we identify when a page was included. This is just a date of publishing. Added30days - if a program was added within last 30 days. Anu: If Program_DateAdded is null then we check previous day (i.e., date - 1, day - 2 ...) and so on for previous ~30 days (or more? we think we can check for 365 days easily). If Program_DateAdded is null for all previous days, we need to have fallback date which is 2019-09-25 Yedige:

Welcome to the Data Portal where you can find a data catalog of openly available data assets. You can quickly download entire catalog of data assets in 3 different formats - RDF, TTL or JSON-LD. You can also use the web application to search, browse and explore data assets. First of all, let's take a look at the home page. It consists of 2 sections - hero section and highlihghts section. The hero section contains the big Portal title, along with the learn more button which brings the user to the FAQ page, which is also acessible by this link in the top of the page. It also contains ways of reaching your data, such as keyword search, data assets counter, and quick links that returns data sorted in specified ways, such as Most Visited, Recently added, Collections view and Geo Spatial data assets. The highlights section features links to relevant documents and a straight link to the most recent added and most viewed data assets.

Current portal We are clear that each timeserie is a table with datetime and a dimension (or metric). A timeserie can be either a CKAN resource or dataset (package): If it's a resource, we can group relevant timeseries in one package. It seems convinient initially. If a timeserie is a dataset (package) with single resource, it can be a lot easier to discover and have metadata indexed easily. It might be useful as a timeserie can have quite rich metadata, eg:DPQTAEJ like this one https://demo.dev.datopian.com/dataset/dpqtaej where we can have full flexibility in terms of title, description, tags, groups + custom metadata (e.g., granularity such as weekly, monthly etc., frequency which indicated udpate frequency etc.) From Luccas: Observations The smallest unity of data in the current portal seems to be a time series, each time series is like a table except that it has only two columns, the date and some data specific to that date. These time series can be joined together by date.

Our inspiration: https://www.youtube.com/watch?v=EPRpE5MT3Q0 Script starts here: With DataHub Enterprise you’ll be able to unlock the potential of your data, by making it easy to find, access and be explored by anyone. DataHub Enterprise is a complete solution for building open data platforms, enterprise data catalogs, data lakes and more. It leverages from a range of proven open-source solutions and integrations with well-known industry leaders. DataHub Enterprise provides extensive data cataloging features. It enables you to describe your data, making it easy for users to discover and explore datasets they need:

Which API endpoint is called? We understand from your response that API endpoint call can be tracked via Google Analytics. But is it possible to build/develop this feature in CKAN? If yes, then will this require medium OR extensive development? Answer: Yes, it is possible to build this feature in CKAN itself. Generally, we think it would require 'medium' development effort, e.g., 2-3 weeks depending on team's expertise. What parameter & values are passed in the GET request to the API? In the below example we are passing the following parameters & values to CKAN API (in a CKAN table we have a field for resourceId, the resourceId value passed in the API, will be checked against this field. Note: a user can use Postman application to pass these parameters & values). So, can CKAN API track this OR do we need to build custom code?

Communication in a remote and flat company Commitment to communicate effectively Commitment to proactively communicate especially about things especially things that are not working as well as we would like This is key in all teams and all organizations and it is especially important for us as we are: a) remote b) relatively flat (self-managing, autonomous).