Luhn ID

[Elaine Baker]

Instedd -

We wanted to ask about the generation of the Luhn ID - is RM doing this or the curation tool doing this?  Note that if RM is doing it, we want RM to do it for the public collection only but not for the curation collection, becuase the Luhn ID should be generated only on approval (ie a facility which is requested to be created and rejected will never receive a Luhn ID). 

After approval, the curation tool will simply insert the Luhn ID  into the curation collection (as generated by either RM public collection or the curation module).

Let us know which way it will be done.

Thanks
Elaine

--

Elaine Baker
Systems Analyst

+255715568512

[Scott Teesdale]

Hi Elaine, 

Good question.  Resource Map is currently generating the Luhn ID.  Since I did a direct copy of the public collection for the curation collection they are both currently generating the Luhn ID.   I think the appropriate next is to remove the field Luhn ID in the curation collection as it won't be used until a record is approved and passed to the public collection.  

If you have time, could you try to edit the Resource Map curation collection schema to resolve this issue?  I think it will be helpful for UCC to get more comfortable with the  collection schema designer.  This one is a pretty quick fix.  Here is a link to the collection's layer settings.  http://resourcemap.instedd.org/collections/463/layers.   First look for the Layer called " Facility Identifier Number"  and then you can either edit the layer and remove the field/make it a text form field or remove the whole layer since it is the only field in the layer.

  

Let me know if you have any questions and of course I am happy to do a quick screen share as well.  I also just added your elaine.baker.work account as an admin to the curation collection as I saw you were not yet a member. 

Best,

Scott 

--
You received this message because you are subscribed to the Google Groups "hfr-tz" group.
To unsubscribe from this group and stop receiving emails from it, send an email to hfr-tz+un...@googlegroups.com.
To post to this group, send email to hfr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--

Scott Teesdale

Project Manager - InSTEDD

Email: stee...@instedd.org 

Skype: scott.teesdale 

Social: Twitter / LinkedIn 

[Elaine Baker]

Thanks Scott

Issue is we don't want to remove the Luhn ID from the curation collection (as it will be used in cases of data being edited for matching records between curation and public collections), but rather set it just as an ordinary field where we post the data in, and not have it auto-generate.  The auto-generation can be retained for the public collection.
Best wishes
Elaine

[Esther Msechu]

Dear Team

I am inviting you to the meeting to discuss broadly on HFR finalization and scale-up plan on Monday, 10:00 AM at MoHSW, Head of ICT office.

Regards

E. Msechu

[Carolina Hadad]

Hello Elaine!

Actually, what ResourceMap does is to autogenerate the luhn value ONLY if there is not a value in the POST request. If a value is provided, then it uses it (if it is valid -luhn check, format and uniqueness in the collection-).

So, you should be able to have the luhn field in both collection: In the curation tool, since the value does not exists yet, ResourceMap will generate a new one; and in the public one, since you create the facility with an existing luhn value - the matching one from the curation collection- ResourceMap will keep this value.

Best,

Caro

2013/10/25 Elaine Baker <elaine.b...@gmail.com>

--

Carolina Hadad

Manas Technology Solutions

[ar.phone] 4796.0232

[us.phone] 312.612.1050

[email] cha...@manas.com.ar

[web] man.as/caro

[Elaine Baker]

Ok that's good.  Can we pass a null value or zero length string or 000000-0 or something like that when creating a site in the curation collection to prevent a value auto-generating?  Of course it can be updated with the real Luhn ID if the site is approved, but it would just be confusing and it might do some harm if the ID generated in the curation collection happened to be the same as a real ID of another site in the public collection, as then sites would be mismatched in queries.

Best wishes
Elaine

[Martin Verzilli]

Another option would be to turn off the Luhn behavior in the LuhnId field of the curation collection's schema from RM. 

That would cause that field to behave as a "normal" identifier, without all the additional checks that RM puts on top of it, so in terms of functionality the field becomes a free text field. 

[Elaine Baker]

That sounds good and looks like the simplest option.  Can you do that please? (Or Michael and Robert can you do it?)

Thanks
Elaine