Feature request - allow for a change of name in a repository after creation

[colinpmillar]

Summary

A user would like to be able to change the name of the repository from:

ices-taf/2020_pra.27.3a4a_assessment

to

ices-taf/2020_pra.27.3a4a_assessment-advice2020

This will likely come up again, but may not be a high priority.

The reason is that there is a second assessment for advice in 2021, and when we added this assessment, it seemed a good idea to change the frst repo from the default name.

[jensr]

Should this be a documented naming convention that takes account of this? Or is it a relatively rare occurrence?

[colinpmillar]

It came up due to the nameing convention including an almost free text feild. Specifically we had:

1. {year}_{stock_code}_assessment
2. {year}_{stock_code}_assessment_advice2021

and the advice 2021 part is free text to allow the users to create multiple repos within a type. In this case the full assessment comprises 2 assessments, one for advice in 2020 and the other for advice in

2021. After thinking aout it the assessors would have prefered to have had, hence the request

2022. {year}_{stock_code}_assessment_advice2020

2023. {year}_{stock_code}_assessment_advice2021

[jensr]

A couple of daft questions maybe - but perhaps the naming convention should be made a little broader as well (e.g. if TAF is begin used for other types of assessments? Also is year = the year in which you are running the assessment or the year you are assessing?

Perhaps widening the scheme to: year = year of activity/work - not representative of the data or forecast period EG = name of expert group or workshop conducting the assessment Assessment type = e.g. different stock categories, IEA or other assessment types (ideally from an ICES vocab) Assessment target = e.g. specific stocks, areas, periods Versions/variants = freetext space for variants

But it might be too complcated or generate names that are too long?