Re: [Gramps-devel] Merging editsource and editcitation

[Benny M. <ben...@gm...>]

2013/6/5 Helge.Herz <Hel...@we...>

> Benny,
>
> that looks really interesting for me to have such a lot possibilities to
> enter data.
> I'm not sure if I'm confused because of the current intermediate state
> of the branch for GEP18.
> But e.g. currently I see two possibilities to enter data for a
> repository:  one is part of the Source Template the second is the
> Repository as before.
> What's your idea to handle this for the final version?
>

Repository and repository location will be taken from the repository list,
not the attrbute. If the user however makes an explicit repository
attribute, that will take precedence.
Note that even if repository is known, user can store optionally short
versions as attributes, wish in the sense of EE will then be used in the
short version of the reference (in EE this is on second appearance of same
citation).  I added short versions yesterday.

>
> Second topic:
> I like the idea of the source templates.
> But the pure count of possibilities is confusing me too. In the past I
> did try to enter all information like these more or less consequent into
> the current available fields. What is your idea for the user to
> transform already available data values into these fields?
>

I intend to rename the All section to Basic templates, of which the first
is GEDCOM and for which hopefully some other basic templates are added like
on the simple citations  website (although in my view that there is not
well worked out)

As on new source/citation, the default will be one of the basic templates,
it will only be confusing to people if they want to use the EE templates
but don't know EE. I'm not sure we can do much about that, except make sure
the help in the manual is clear.

>
> Third topic:
> I tried also to enter some data values into Source Template fields
> (Attributes) using one or two versions earlier. Now it seems to me that
> values I did enter e.g. for Attribute-Type X now will be used as value
> for Attribute-Type Y. I assume it happens because of some current
> changes. But I thought there would be a reference by name to be sure
> that all data values will be fix related to an attribute name. At least
> if there are changes after any release. So I wonder if this did happen.
>

There have been changes, and there will be again soon. I intend to merge
more fields. As this is a development branch, I renumber types, so type X
will become type Y. Once attribute types are fixed, numbers for types are
frozen, and type will no longer change.

The reason to merge fields is to allow people to change source template,
and not need to retype attributes as the name changed slightly. The
description in the GUI will still change, but the attributetype in database
will be the same.

Benny


>
> - Helge
>
>
>
> ------------------------------------------------------------------------------
> How ServiceNow helps IT people transform IT departments:
> 1. A cloud service to automate IT design, transition and operations
> 2. Dashboards that offer high-level views of enterprise services
> 3. A single system of record for all IT processes
> http://p.sf.net/sfu/servicenow-d2d-j
> _______________________________________________
> Gramps-devel mailing list
> Gra...@li...
> https://lists.sourceforge.net/lists/listinfo/gramps-devel
>