Hi Utsav,
That's actually how it's currently done. I would suggest that you really
take a look at the current code base. I think you'll find that many of
your suggestions/discoveries are already implemented in Arches.
Feel free to step into the code and really dig into it.
Cheers,
Alexei
Direct
Status Update (April 10, 2014):
Arches received 2 slots for the 2014 Google Summer of Code. Thanks to
everyone who participated and who submitted a proposal. We received
several good proposals which we are in the process of reviewing and
prioritizing. Remember, even if you are not chosen to
Hiii,
-->On getting User formed geometries from the browser !!
Openlayers Geometry library has a function toString() that detects all the
geometry from the browser and displays those geometries in WKT format.
This WKT format can be passed to *.values.csv to associate the geometry
with any co
OK, the error did not have anything to do with our modified Authority
Documents.
It was caused by the entry to limit Resource Types in the global
settings.py:
LIMIT_ENTITY_TYPES_TO_LOAD = (
# override this setting in your packages settings.py file
'ARCHAEOLOGICAL HERITAGE (SITE).E27',
)
Dear Archeslist,
we have extended the ARCHAEOLOGICAL HERITAGE (SITE).E27 Resource Type and
defined our own vocabularies in the according Authority Files.
(After running install_arches_db.sh and build.sh), install_packages.sh
loads all Authority Files. However the function
create_link_to_entity
