Renaming "data provision" page title #25

Closed
opened 2022-12-05 14:45:11 +01:00 by claudio.atzori · 5 comments

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

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.
Member

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".
Collaborator

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?
Author
Owner

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.
Member

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.
No Label
No Milestone
No project
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.