You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The units service will almost always be behind the lands division, which is also never going to be up-to-date. Some valid units in the units geography service will not have geography associated with them.
Invalid units and units without geography return the same result from the units API service for geography
This will require a 3-step process:
a) An initial API call to verify whether a unit is valid or not
b) A secondary API call to get geography, if it exists
c) Adding the content unit - with or without geography - to EML
It will be important to verify that DataStore can handle content units without geography in metadata:
a) When some content units have geography and some do not
b) When none of the content units have geography
c) When all of the content units have geography
The units service will almost always be behind the lands division, which is also never going to be up-to-date. Some valid units in the units geography service will not have geography associated with them.
Invalid units and units without geography return the same result from the units API service for geography
This will require a 3-step process:
a) An initial API call to verify whether a unit is valid or not
b) A secondary API call to get geography, if it exists
c) Adding the content unit - with or without geography - to EML
It will be important to verify that DataStore can handle content units without geography in metadata:
a) When some content units have geography and some do not
b) When none of the content units have geography
c) When all of the content units have geography