Bienvenue, Invité
Nom d'utilisateur : Mot de passe :
Before asking for help please read "How to request help" by clicking on that tab above here.
  • Page :
  • 1

SUJET :

defining gedcom tags il y a 2 semaines 3 jours #1

  • guidovanharten
  • Portrait de guidovanharten Auteur du sujet
  • Absent
  • Junior
  • Junior
  • Messages : 203
In gedcom 5.5.1 it is allowed to use custom (user defined) gedcom tags
1 FCM
2 DATE 1 APR 1865

webtrees displays these gedcom tags in a red font (Unknown gedcom code).
I guess there should be an option to define these gedcom tags (FCM means member of the football club).
Does webtrees this function?

Best regards,
Guido

Connexion ou Créer un compte pour participer à la conversation.

defining gedcom tags il y a 2 semaines 3 jours #2

  • thomas52
  • Portrait de thomas52
  • Absent
  • Frequent
  • Frequent
  • Western North Carolina
  • Messages : 882
"Failure is an amazing teacher." (L'échec est un professeur extraordinaire.)

Connexion ou Créer un compte pour participer à la conversation.

defining gedcom tags il y a 2 semaines 3 jours #3

  • fisharebest
  • Portrait de fisharebest
  • Hors Ligne
  • Administrator
  • Administrator
  • Messages : 13196
In webtrees 2.0, you must modify the code.

But in webtrees 2.1, custom tags are defined by modules, so it is easy to add your own.

2.1 is mostly complete. Perhaps two more months?
Greg Roach - Cette adresse e-mail est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. - fisharebest.webtrees.net

Connexion ou Créer un compte pour participer à la conversation.

defining gedcom tags il y a 2 semaines 3 jours #4

Guido,

A user defined tag for football club would not be “FCM”. This would be incorrect GEDCOM.

The most common way and in keeping with the spirit of the most recent version of GEDCOM would be to build a tag that looks like:

1 FACT member
2 TYPE football club

Or

1 FACT
2 TYPE football club member


I would recommend this as your solution since no other program reading a GEDCOM you produced would understand the code/tag you are proposing.
Ken

Connexion ou Créer un compte pour participer à la conversation.

Dernière édition: par norwegian_sardines.

defining gedcom tags il y a 2 semaines 3 jours #5

  • guidovanharten
  • Portrait de guidovanharten Auteur du sujet
  • Absent
  • Junior
  • Junior
  • Messages : 203
@norwegian_sardines, I think you are wrong.
I used other family tree programs where user defined gedcom tags use these syntax.
Be aware that the gedcom tag is not one of the default/standard tags, has no spaces, and (I'm not sure) is max. 5 characters long.
This way is more flexible than FACT or EVEN.
It's also possible to use parameters (notes) to the custom tag:

1 FCM keeper
2 DATE 1 DEC 1853
1 FCM chairman
2 DATE 1 APR 1865

Best regards,
Guido

Connexion ou Créer un compte pour participer à la conversation.

defining gedcom tags il y a 2 semaines 3 jours #6

norwegian_sardines écrit: Guido,

A used defined tag for football club would not be “FCM”. This would be incorrect GEDCOM.

The most common way and in keeping with the spirit of the most recent version of GEDCOM would be to build a tag that looks like:

1 FACT member
2 TYPE football club

Or

1 FACT
2 TYPE football club member


I would recommend this as your solution since no other program reading a GEDCOM you produced would understand the code/tag you are proposing.


I 100% agree with Ken on this. Custom tags should only extremely rarely be necessary.

But if you insist on using them, then do please read the rest of the GEDCOM spec about them. They MUST always be prefixed with an underscore character. So “_FCM” not “FCM“.
Nigel

www.our-families.info

Hosted at:
Follow me at:

Connexion ou Créer un compte pour participer à la conversation.

defining gedcom tags il y a 2 semaines 3 jours #7

  • fisharebest
  • Portrait de fisharebest
  • Hors Ligne
  • Administrator
  • Administrator
  • Messages : 13196
To be compatible with GEDCOM standards, these tags should begin with _

So, you should use

1 _FCM keeper
2 DATE 1 DEC 1853
1 _FCM chairman
2 DATE 1 APR 1865

This is valid GEDCOM.

But GEDCOM also says that applications should ignore all custom tags that they do not recognise.

So, this data is good - but only if it stays inside systems that understand _FCM.

webtrees will keep all your custom tags - even if it does not know what they are.
Other applications may not.
Greg Roach - Cette adresse e-mail est protégée contre les robots spammeurs. Vous devez activer le JavaScript pour la visualiser. - fisharebest.webtrees.net

Connexion ou Créer un compte pour participer à la conversation.

defining gedcom tags il y a 2 semaines 3 jours #8

Guido,

I’ve been involved with the GEDCOM standard since the mid/late1980s, longer than many of these programs have been around. Most of these programs don’t understand the GEDCOM standard and have little regard for building proper GEDCOM so you can transport data between programs.

Please review the advice of Greg and Nigel as indicated above.

Also, please understand that the EVEN and FACT tags have no restrictions on the sub tags that are possible. You are more than able to include NOTE, PLAC, DATE, SOUR, etc. sub tags on these two custom types.

I would be more than happy to help you build GEDCOM compliant using the sub tags available in the standard. For example:

1 FACT keeper
2 TYPE football club member
2 DATE 1 DEC 1853
2 PLAC your town, Germany
2 NOTE Had a very high save ratio

1 FACT chairman
2 TYPE football club member
2 DATE 1 APR 1865
Ken

Connexion ou Créer un compte pour participer à la conversation.

Dernière édition: par norwegian_sardines.
Avez-vous besoin d'une solution d'hébergement web pour votre site webtrees ?
Si vous préférez un hébergeur spécialisé de webtrees, la page suivante en liste quelques-uns capables de vous offrir ce type de service :
  • Page :
  • 1
Propulsé par Kunena