D-Net
/
openaire-graph-docs
6
1
Fork 5
Code Issues 5 Pull Requests 2 Packages Projects Releases 67 Wiki Activity

Renaming "data provision" page title #25

New Issue
Closed
opened 2022-12-05 14:45:11 +01:00 by claudio.atzori · 5 comments
claudio.atzori commented 2022-12-05 14:45:11 +01:00
Owner
Copy Link

I'm tempted to rename the "data provision" section. The term "provision" is consolidated in our internal jargon, and it mostly refers to the final graph materialisation phases (indexing, stats analysis), while here instead we are using it to document the entire set of processes, from end to end.

Here are the options I have in mind:

  • "Data pipeline",
  • "Graph pipeline",
  • or just "Pipeline"

What are your opinions?

We should

I'm tempted to rename the "data provision" section. The term "provision" is consolidated in our internal jargon, and it mostly refers to the final graph materialisation phases (indexing, stats analysis), while here instead we are using it to document the entire set of processes, from end to end. Here are the options I have in mind: * "Data pipeline", * "Graph pipeline", * or just "Pipeline" What are your opinions? We should * rename the title avaiable here:https://code-repo.d4science.org/D-Net/openaire-graph-docs/src/commit/029429fcc5fc815d77f9ab97c2e87f40159f88bb/docs/data-provision/data-provision.md#L1 * rename the markdown file * update the references to that file
alessia.bardi was assigned by claudio.atzori 2022-12-05 14:45:11 +01:00
miriam.baglioni was assigned by claudio.atzori 2022-12-05 14:45:11 +01:00
schatz was assigned by claudio.atzori 2022-12-05 14:45:11 +01:00
thanasis.vergoulis was assigned by claudio.atzori 2022-12-05 14:45:11 +01:00
miriam.baglioni commented 2022-12-05 16:51:26 +01:00
Member
Copy Link

I agree. From the three the one I prefer is Data Pipeline since we describe how data are ingested and updated and finally used.

I agree. From the three the one I prefer is Data Pipeline since we describe how data are ingested and updated and finally used.
schatz commented 2022-12-14 19:44:30 +01:00
Member
Copy Link

From a discussion we had today, some other options were mentioned, such as:

  • Data workflow
  • ETL workflow (?)

Please, @thanasis.vergoulis can you elaborate on this so that we come to an aggreement?
Personally, from these options I would go for "Data Pipeline".

From a discussion we had today, some other options were mentioned, such as: * Data workflow * ETL workflow (?) Please, @thanasis.vergoulis can you elaborate on this so that we come to an aggreement? Personally, from these options I would go for "Data Pipeline".
thanasis.vergoulis commented 2022-12-18 10:38:38 +01:00
Collaborator
Copy Link

Yes. I prefer the term "workflow" over "pipeline" (it is easier to understand for the average reader). I would go with "Data Workflow" but I think it sounds incomplete. What would you think about "Graph production workflow"???

Alternatives:

  • "Data processing workflow"
  • "Data production workflow"
  • "ETL workflow"

But I would prefer the "Graph production workflow" term... Opinions?

Yes. I prefer the term "workflow" over "pipeline" (it is easier to understand for the average reader). I would go with "Data Workflow" but I think it sounds incomplete. What would you think about "Graph production workflow"??? Alternatives: - "Data processing workflow" - "Data production workflow" - "ETL workflow" But I would prefer the "Graph production workflow" term... Opinions?
claudio.atzori commented 2022-12-19 12:06:59 +01:00
Author
Owner
Copy Link

Graph production workflow, semantically speaking, seems quite complete. It might be graphically a bit large for the section sidebar, but a part from this, I think we could go for it.

_Graph production workflow_, semantically speaking, seems quite complete. It might be graphically a bit large for the section sidebar, but a part from this, I think we could go for it.
schatz commented 2022-12-20 16:56:31 +01:00
Member
Copy Link

Ok let's go with Data production workflow then. Thanks!

Ok let's go with *Data production workflow* then. Thanks!
Sign in to join this conversation.
main
Branches Tags
Clear current reference
main
v9.0.0
dataset_vs_data
10084/cursor_pagination_date_format
v8.0.0
v7.0.0
graph-api-docs
graph-api-docs-fix-links
pivotselectionbypid
pid_stability
update_affiliation_algorithms
v7.1.3
v7.1.1
dedup_v4
upgrade-docusaurus-3
api
SWH
updateScholixLink
marekhorst_fixing_citationmatching_references
marekhorst_fixing_citationmatching_short_descr
v6.0.0_fix
v6.1.0
8925
v6.0.0
pdf_aggregation
marekhorst_52_extraction_of_cited_concepts_refinement
v5.1.3
8549_affiliation_extraction
scholexplorer_ds
opencitations
Change_graph_name
5.1.0
relation_provenance
changelog
beginners-kit
graph-data-model-revision
restructure_data_provision
enable_search
fix-image-links
parameter_config_with_env
disable_color_theme_switch
update_badges
update_related_datasets
dumpSubset
bulk_downloads
release_properties
reduced_image_file_size
aggregation
fix_issues_raised_in_PR_7
styling
Add_sitemap_generation
enrichment
formating_enrichment_section
enrichment_mining_icm
update_docusaurus
impact_indicators
openaire_graph_rename
indexing
license
learning-center
cleaning
Clear current reference
9.0.0
8.0.0-3
8.0.0-2
8.0.0-1
8.0.0
7.1.3-22
7.1.3-21
7.1.3-20
7.1.3-19
7.1.3-18
7.1.3-17
7.1.3-16
7.1.3-15
7.1.3-14
7.1.3-13
7.1.3-12
7.1.3-11
7.1.3-10
7.1.3-9
7.1.3-8
7.1.3-7
7.1.3-6
7.1.3-5
7.1.3-4
7.1.3-3
7.1.3-2
7.1.3-1
7.1.3
7.1.1
7.1.0-1
7.1.0
7.0.0-6
7.0.0-5
7.0.0-4
7.0.0-3
7.0.0-2
7.0.0-1
6.2.2.3
6.2.2.2
6.2.2.1
6.2.2
6.1.1-1
6.1.1-0
6.1.1
v.6.0.0-3
6.0.0-2
6.0.0-1
6.0.1
6.0.0
5.2.0
5.1.3-1
5.1.3
5.1.2-5
5.1.2-4
5.1.2-3
5.1.2-2
5.1.2-1
5.1.2
5.1.0-6
5.1.0-5
5.1.0-4
5.1.0-3
5.0.1-2
5.1.0-1
5.1.0
5.0.0-1
5.0.0
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
thanasis.vergoulis
schatz
miriam.baglioni
alessia.bardi
4 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: D-Net/openaire-graph-docs#25
No description provided.
Delete Branch "%!s(<nil>)"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?