# Name configuration for reader pipeline source
**URL:** https://discourse.paraview.org/t/name-configuration-for-reader-pipeline-source/10541
**Category:** Development
**Created:** [October 18, 2022, 7:48am UTC](https://discourse.paraview.org/t/name-configuration-for-reader-pipeline-source/10541 "2022-10-18T07:48:36Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@nicolas.vuaille](https://discourse.paraview.org/u/nicolas.vuaille)
#### Post date: [October 18, 2022, 7:48am UTC](https://discourse.paraview.org/t/name-configuration-for-reader-pipeline-source/10541/1 "2022-10-18T07:48:36Z")
Hi community,
When loading a file, the pipeline source created is named according to the file, including extensions.
This is not always the best choice:
- this may be a generic name given by the solver, whereas the meaningful part (specifc run informations) may be in the directory name, or elsewhere (inside the file for instance)
- when working with catalyst, we may prefer to have a generic input name, known as the channel name, so the exported script is always consistent with the simulation adaptor.
### Proposition
In the `Open File` reaction, we can check for an Information `StringVectorProperty`. Let’s call it `PipelineSourceName`. If this property exists in the reader proxy, we use it to set the pipeline source name. Otherwise, we use the filename as usual.
Any thought ?
@cory.quammen @mwestphal
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [October 18, 2022, 7:53am UTC](https://discourse.paraview.org/t/name-configuration-for-reader-pipeline-source/10541/2 "2022-10-18T07:53:28Z")
In case this is not clear for all reader, `Information Property` value are provided by the server and read by the client, contrary to classic properties.
For the specific topic, I’d say that it seems like a fair approach.
---
### Author:  [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 18, 2022, 11:01am UTC](https://discourse.paraview.org/t/name-configuration-for-reader-pipeline-source/10541/3 "2022-10-18T11:01:56Z")
Sounds reasonable.
---
### Author:  [@Andy\_Bauer](https://discourse.paraview.org/u/Andy_Bauer)
#### Post date: [October 18, 2022, 4:26pm UTC](https://discourse.paraview.org/t/name-configuration-for-reader-pipeline-source/10541/4 "2022-10-18T16:26:12Z")
Need to keep in mind that when generating ParaView Catalyst pipelines that the pipeline name for the reader has a correspondence with the channel name. Additionally, for ParaView Catalyst generated datasets the reader switches the pipeline name to the channel name.
---
### Author:  [@nicolas.vuaille](https://discourse.paraview.org/u/nicolas.vuaille)
#### Post date: [November 8, 2022, 11:34am UTC](https://discourse.paraview.org/t/name-configuration-for-reader-pipeline-source/10541/5 "2022-11-08T11:34:04Z")
This has been implemented in this [MR](https://gitlab.kitware.com/paraview/paraview/-/merge_requests/5973#note_1273379).
If an information property called `RegistrationName` is found, it is used to rename the pipeline source.
See this [example](https://gitlab.kitware.com/paraview/paraview/-/tree/master/Examples/Plugins/ReaderName/Plugin) for usage.