Observed data: extended properties without name

[Yuri05]

It happens from time to time that serialized observed data sets have extended properties without a name:

...
  <ExtendedProperties>
    ...
    <StringExtendedProperty readOnly="0" />
  </ExtendedProperties>
...

s e.g.

• Error in loading a project in PK-Sim PK-Sim#1589
• PK-sim suddenly gives een error when opening the model, can I retrieve it? PK-Sim#2875
• PK sim file shows error after opening PK-Sim#2894

In such a case, the whole project cannot be loaded at all.
While the problem (during observed data import?) is still not reproducible, we could try to catch it somewhere.

• e.g. additionally to the value, check that the name of the extended property is not null or empty before adding it?
  

  OSPSuite.Core/src/OSPSuite.Infrastructure.Import/Core/Mappers/DataSetToDataRepositoryMapper.cs

  Lines 39 to 44 in 0d01657

  	foreach (var metaDataDescription in dataSet.MetaDataDescription)
  	{
  	if (!metaDataDescription.Value.IsNullOrEmpty())
  	dataRepository.ExtendedProperties.Add(new ExtendedProperty<string>()
  	{ Name = metaDataDescription.Name, Value = metaDataDescription.Value });
  	}

• or adjust the onMissingKey argument when adding an extended property (so that if the name is null or empty it will be replaced with some dummy name)? Does not make much sense but at least it would not crash
  

  OSPSuite.Core/src/OSPSuite.Core/Domain/ExtendedProperties.cs

  Line 9 in 0d01657

  public ExtendedProperties() : base(x => x.Name)

[Yuri05]

@msevestre @rwmcintosh Thoughts on this?

[rwmcintosh]

Dummy name would at least prevent it from being lost during import. Can the name be changed after?

[Yuri05]

If it's not one of the predefined names (e.g. "Organ", "Molecule") - yes, it can be changed later.